Manifest.json Package.json
Kris Kowal
There is a lot of overlap between Chrome Application Manifests and
CommonJS and NPM package descriptions. This might be intent or
convergent evolution—I don’t know.
http://code.google.com/chrome/extensions/manifest.html
http://npmjs.org/doc/json.html
http://wiki.commonjs.org/wiki/Packages/1.0
The only major divergence is "name", which precludes consolidating the
two files in most cases.
For a manifest, the "name" is a title like "My Application", whereas
in package.json, "name" is name suitable for identification in a
package registry, like "my-application".
I am recommending that CommonJS / NPM reserve "title" for the purpose
of a name, suitable for placement in a window title, like "My
Application".
https://github.com/kriskowal/uncommonjs/blob/master/packages/specification.md
In a future version, Chrome could check for the existence of a "title"
property and ignore "name" if one is present. That would open the
possibility of consolidating these files in certain applications.
Kris Kowal
Kris Kowal
> Can you file a ticket at http://new.crbug.com/ and post the ID here?
Thanks. Submitted 114954
http://code.google.com/p/chromium/issues/detail?id=114954
Mozilla appears to be tracking the format as well. I’m not sure who to
bother about that.
https://developer.mozilla.org/en/Apps/Manifest
Kris Kowal
Panagiotis Astithas
I think posting to the mozilla-labs mailing list would be the best way to contact the right people. Here is a somewhat recent post on a relevant subject:
https://groups.google.com/forum/?fromgroups#!topic/mozilla-labs/KdGGvS81gOQ
--
Panagiotis Astithas
http://astithas.com