874
edits
(→Undocumented Features: shortened local.json example) |
(→Packages: added info on fullName) |
||
| Line 27: | Line 27: | ||
<tt>package.json</tt> may contain the following keys: | <tt>package.json</tt> may contain the following keys: | ||
*<tt>name</tt> - the name of the package. The package system will only load one package with a given name. The name defaults to the name of the parent directory. If the package is ever built as an XPI, this is used as the extension's <tt>em:name</tt> element in its <tt>install.rdf</tt>. | *<tt>name</tt> - the name of the package. The package system will only load one package with a given name. This name cannot contain spaces. The name defaults to the name of the parent directory. If the package is ever built as an XPI and the <tt>fullName</tt> key is not present, this is used as the extension's <tt>em:name</tt> element in its <tt>install.rdf</tt>. | ||
*<tt>fullName</tt> - the full name of the package. It can contain spaces. If the package is ever built as an XPI, this is used as the extension's <tt>em:name</tt> element in its <tt>install.rdf</tt>. | |||
*<tt>description</tt> - a String describing the package. If the package is ever built as an XPI, this is used as the extension's <tt>em:description</tt> element in its <tt>install.rdf</tt>. | *<tt>description</tt> - a String describing the package. If the package is ever built as an XPI, this is used as the extension's <tt>em:description</tt> element in its <tt>install.rdf</tt>. | ||
edits