I personally like to default to MIT, and much of the rest of the Node.js ecosystem does the same. The first default is the initial license that will be automatically suggested by the npm init command. This personal information won't change too frequently, so setting up some defaults is helpful and allows you to skip over entering the same information in manually every time.Īdditionally, the above commands set up two defaults that are related to your module. In the above example, I've set up some defaults for Hiro.

You can easily set your name, email, URL, license, and initial module version with a few commands: npm config set 'Hiro Protagonist' commands that set default values for the npm init prompts. One thing that some developers don't know is that you can actually automate this process fairly heftily with a few choice npm config set. When you're creating a new module from scratch, you'll typically start out with the npm init command. npmrc allows that have been awesome for speeding up my personal workflow when scaffolding out Node.js modules and working on applications long-term. So, today I've collected a few of the optimizations that. npmrc file could be, or how to even use it. For a long time, I didn't truly understand just how useful the. For a long time I'd seen discussion about it - the most memorable being the time I thought you could change the name of the node_modules directory with it. One part of this high-configurability is the. It provides an enormous amount of configurability that enables everyone from huge enterprises to individual developers to use it effectively. One of the most useful, important, and enabling aspects of the npm CLI is that its highly configurable. It's literally something we interact with multiple times on a daily basis, and it's one of the pieces of the ecosystem that's led to the success of Node.js. For Node.js developers, npm is an everyday tool.

Npm config set version