Fix the package.json formatting to allow for better parsing by NPM #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull request formats the
package.json
file to use standard JSON formatting.While the existing
package.json
file is technically valid JSON, it uses non-standard formatting which actually breaks some features innpm install
.For example, when running
npm install
, and inspecting the resultingpackage.json
file inside of thenode_modules
folder, there are a few fields missing, namely the'license'
field.