The package.json file holds all of the information about the package we are trying to build. It even gives us the ability to tie it into our version control system, and we can even tie it into our build system. Let's go over this now.
First, a package.json file should have the following fields filled out:
- name: This is the name of the package.
- version: This is the current version of our software package.
- type: This should either be module or commonjs. This will allow us to distinguish between legacy systems and the new ECMAScript module system.
- license: This is how we want to license our module. Most of the time, just go ahead and put the MIT license. However, if we do want to lock it down more, we could ...
