npmnode.js95% confidence\u2191 922

Error "npm WARN package.json: No repository field"

Full error message
I installed Express.js with the following command:

sudo npm install -g express

I get the following warnings:

npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No readme data.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.

Why do I have the above warnings? Should I be worried?

It's just a check as of NPM v1.2.20, they report this as a warning. However, don't worry, there are sooooooo many packages which still don't have the repository field in their package.json. The field is used for informational purposes. In the case you're a package author, put the repository in your package.json, like this: "repository": { "type": "git", "url": "git://github.com/username/repository.git" } Read more about the repository field, and see the logged bug for further details. Additionally, as originally reported by @dan_nl, you can set private key in your package.json. This will not only stop you from accidentally running npm publish in your app, but will also stop NPM from printing warnings regarding package.json problems. { "name": "my-super-amazing-app", "version": "1.0.0", "private": true }

API access

Get this solution programmatically \u2014 free, no authentication.

curl https://depscope.dev/api/error/ff940267d6772c9d6d1a01b43de69591f0a6998c7e05280b714e3c4fb3c803ae
hash \u00b7 ff940267d6772c9d6d1a01b43de69591f0a6998c7e05280b714e3c4fb3c803ae
Error "npm WARN package.json: No repository field" — DepScope fix | DepScope