0

When I use npm on one of my home workstations, it always adds a package-lock.json file. It also creates this file when I pull down massive work repositories, and it is griefing me and my team because it pollutes pull requests by adding this 155kb file.

My workstation at work is setup almost identical, so I'm curious why this one PC creates this file.

Is there a global config setting or something I can toggle to turn this file creation off?

I'd prefer that over adding it to .gitignore in all projects.

I don't see any info helpful to my situation here:

https://docs.npmjs.com/files/package-lock.json

https://docs.npmjs.com/files/package-locks

This post is also useful to describe what package-lock.json is providing:

Do I need both package-lock.json and package.json?

agm1984
  • 15,500
  • 6
  • 89
  • 113

1 Answers1

1

To tell npm not to create a package-lock.jsonlock file for your current project, create a file called .npmrc at the root of the project and add package-lock=false to it.

If you want completely disable package-lock.json creation on your machine, simply set the config globally.

npm config set package-lock false
alexmac
  • 19,087
  • 7
  • 58
  • 69