As of lit 1.1.3, newly created packages will store their metadata as a JSON
blob in the git tag. This will enable much faster and simpler queries on
the repo database. It also has a whitelist of metadata fields that are
included in this list.
The recognized keys are similar to npm's package.json:
- name - a string in the form "username/packagename"
- version - A string in the form "x.y.z" like "1.0.0" or "0.2.3"
- description - A description (can be markdown) to be included in search
listings.
- keywords - A table of string keywords used to index packages by tag.
- homepage - String to the url where the source code, documentation, etc
can be found.
- license - A short license like "MIT" or "Apache 2", etc.
- author - a table in the form {
name = "Tim Caswell",
email = "[email protected]",
url = "http://creationix.com";
}
- contributors - a list of people in the same format as author.
- dependencies - a list of strings in the format "foo/[email protected]",
"luvit/require", etc..
- luvi = a table in the format {flavor="regular", version="2.0.3"} - used
for luvi apps to specify which luvi version that want to use.
Start adding as many of these fields as make sense to your package.lua and
single-file package exports now. As more packages are published with the
new lit we'll have more data to use to query for packages.
--
You received this message because you are subscribed to the Google Groups
"luvit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
