← Back to Releasing JavaScript
A tour of the package.json file
The documentation for what goes in package.json
is twofold:
TODO.
name
You can check that the package name is available on npm
with:
npm search <package>
If your name conflicts with an existing project, you can always publish under your own scope. My fork of jQuery could live under the
@danburzo/jquery
name. The first time you publish a scoped package, you need to usenpm publish --access public
.
Configuration for custom tools
Some tools, such as Prettier or ESLint, let you store their configuration in the package.json
file.