description – A freeform string that describes your package. It’s as
simple as that!
•
devDependencies – Again, one I mentioned in the previous chapter,
and it’s simply the same as dependencies, but it names packages that
are only needed during development.
•
directories – This element allows you to describe the structure
your package, things like the location of library components binary
content, man pages, Markdown documentation, examples, and tests.
See the Common JS package specification for details on this.
•
engines – This element allows you to specify what version(s) of Node
your package works on. You can also use this element to define what
version(s) of NPM is capable of properly installing the package.
•
files – When your package is installed as a dependency, NPM will
need to know what files to include. It will by default assume all, but if
you want or need to be specified, then the files element will let you
do that. It works a lot like a .gitignore file, but in reverse: anything
listed in this element will be included, not ignored.
•
Do'stlaringiz bilan baham: |