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

Question

I installed Express.js with the following command:

sudo npm install -g express

I get the following warnings:

npm WARN package.json range-parser@0.0.4 No repository field.
npm WARN package.json fresh@0.1.0 No repository field.
npm WARN package.json methods@0.0.1 No repository field.
npm WARN package.json methods@0.0.1 No readme data.
npm WARN package.json cookie-signature@1.0.1 No repository field.
npm WARN package.json send@0.1.0 No repository field.
npm WARN package.json pause@0.0.1 No repository field.
npm WARN package.json bytes@0.2.0 No repository field.
npm WARN package.json github-url-from-git@1.1.1 No repository field.
npm WARN package.json assert-plus@0.1.2 No repository field.
npm WARN package.json ctype@0.5.2 No repository field.

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

By seeing this question one year later, I realize that I mentally erase all these warnings every time I install npm packages. This is something package developers should maybe be a bit more careful about. — nha, Sep 27 '14 at 11:53
@nha yeah, I usually see those warnings when doing some npm operation and fix them if it's in the package I'm developing. — gustavohenke, Oct 17 '14 at 03:40
for private repos, just add `"private": true` to package.json — chovy, Nov 29 '15 at 10:05

score 1401 · Accepted Answer · edited Nov 27 '21 at 14:30

1401

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
}

edited Nov 27 '21 at 14:30

KyleMit

30,350
66
462
664

answered May 30 '13 at 04:33

gustavohenke

40,997
14
121
129

21

A few months after my answer and I haven't seem any problems so far :) – gustavohenke Sep 01 '13 at 23:28
2

NPM 2.14 now does print an error when `repository` is empty and `private` is set to true. – Blaise Oct 08 '15 at 09:01
9

@Blaise, I don't get any warnings in NPM 3.3.3 by using `private: true` – gustavohenke Jan 06 '16 at 10:50
4

Question, why isnt "private" the default, I mean how many npm projects are created versus how many are actually published, is there really more library code than user code? – Felype Oct 30 '17 at 02:35
The documentation you linked does not explain why the field is required just that it is useful. Technically, it isn't required (warning vs. error) but I am sure someone is going to wonder why the tool cares at all. – Aluan Haddad Feb 04 '18 at 20:58
The answer by wortwart below is more up to date and uses the`"repository"` field instead of the `"url"` shown here – user2490003 Aug 31 '18 at 15:12
Hi @user2490003, his answer includes behaviour that is _not_ documented, according to https://docs.npmjs.com/files/package.json. – gustavohenke Sep 02 '18 at 14:01
@gustavohenke it is possible to configure it by default, in the global configuration "private": true. – Gdaimon Feb 02 '19 at 21:59

score 411 · Answer 2 · answered Apr 29 '14 at 03:38

411

you can also mark the application as private if you don’t plan to put it in an actual repository.

{
  "name": "my-application",
  "version": "0.0.1",
  "private": true
}

answered Apr 29 '14 at 03:38

dan_nl

4,456
1
15
7

wortwart · Answer 3 · 2018-09-03T19:22:07.457

55

As dan_nl stated, you can add a private fake repository in package.json. You don't even need name and version for it:

{
  ...,
  "repository": {
    "private": true
  }
}

Update: This feature is undocumented and might not work. Choose the following option.

Better still: Set the private flag directly. This way npm doesn't ask for a README file either:

{
  "name": ...,
  "description": ...,
  "version": ...,
  "private": true
}

edited Sep 03 '18 at 19:22

answered Sep 15 '14 at 21:11

wortwart

3,139
27
31

Got notified about another user about this answer. Looks like `repository.private` is not documented behaviour (or it is no longer accepted), according to https://docs.npmjs.com/files/package.json. – gustavohenke Sep 02 '18 at 14:06
1

@gustavohenke: Thank you, it seems you're right - `private` as top-level property is the better option anyway. Updated my answer. – wortwart Sep 03 '18 at 19:24

score 48 · Answer 4 · edited Jun 29 '17 at 20:07

48

If you are getting this from your own package.json, just add the repository field to it. (use the link to your actual repository):

"repository" : { 
   "type" : "git",
   "url" : "https://github.com/npm/npm.git"
 }

edited Jun 29 '17 at 20:07

laurent

88,262
77
290
428

answered Feb 28 '14 at 04:03

Brendan Nee

5,087
2
33
32

Thanks for clarifying to use the full github project file link (including `http://` or `https://`! – twknab Feb 22 '17 at 12:15

score 9 · Answer 5 · edited Oct 06 '15 at 16:21

9

Have you run npm init? That command runs you through everything...

edited Oct 06 '15 at 16:21

BladeBarringer

807
6
17

answered Aug 08 '15 at 19:32

achoukah

1,345
2
10
10

score 8 · Answer 6 · edited Jul 19 '17 at 13:56

8

In Simple word- package.json of your project has not property of repository you must have to add it,

and you have to add repository in your package.json like below

and Let me explain according to your scenario

you must have to add repository field something like below

  "repository" : {     
     "type" : "git",
      "url" : "http://github.com/npm/express.git" 
   }

edited Jul 19 '17 at 13:56

Sibiraj

4,486
7
33
57

answered Apr 16 '17 at 20:47

Shashwat Gupta

5,071
41
33

score 7 · Answer 7 · edited May 23 '18 at 17:52

7

If you don't want to specify a repository you can add the following lines to the package.json file:

"description":"",
"version":"0.0.1",
"private":true,

That worked for me.
By adding private, you don't need to link to a repo.

edited May 23 '18 at 17:52

zx485

28,498
28
50
59

answered May 23 '18 at 11:37

Rubin bhandari

1,873
15
20

score 7 · Answer 8 · edited Sep 24 '18 at 06:45

To avoid warnings like:

npm WARN project.com@1.0.0 No repository field.

You must define repository in your project package.json. In the case when you are developing with no publishing to the repository you can set "private": true in package.json

Example:

{
  "name": "test.loc",
  "version": "1.0.0",
  "private": true,
  ...
  "license": "ISC"
}

NPM documentation about this: https://docs.npmjs.com/files/package.json

score 4 · Answer 9 · answered Nov 26 '16 at 10:55

4

this will help all of you to find your own correct details use

npm ls dist-tag

this will then show the correct info so you don't guess the version file location etc

enjoy :)

answered Nov 26 '16 at 10:55

Ian Croasdell

93
2

1

I got a response as '--empty – M.J Jul 27 '19 at 18:27

score 3 · Answer 10 · answered Apr 27 '16 at 05:12

3

Yes, probably you can re/create one by including -f at the end of your command

answered Apr 27 '16 at 05:12

Jsalim

51
4

score 0 · Answer 11 · answered Aug 18 '22 at 06:44

0

Try: npm install package.json, npm audit fix --force, ncu -u

answered Aug 18 '22 at 06:44

muli

47
1
3

score -1 · Answer 12 · edited Sep 06 '19 at 20:31

-1

use npm install -g angular-cli instead of
npm install -g@nagular/cli to install Angular

edited Sep 06 '19 at 20:31

jimboweb

4,362
3
22
45

answered Sep 06 '19 at 18:38

Alnebras Murtada

13
8

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

12 Answers12

Linked

Related