* Expanded the solution for the 'Get Route Parameter Input from the Client' challenge * Expanded the guide for the 'Use body-parser to Parse POST Requests' challenge * Rewritten guide for the 'Serve JSON on a Specific Route' challenge and fixed source link * Expanded the guide for the 'Serve Static Assets' challenge * Expanded solution to the 'Get Query Parameter Input from the Client' challenge and fixed links to source file * Added solution to the 'Chain Middleware to Create a Time Server' challenge and fixed link to source file * Rewrite the 'Start a Working Express Server' challenge * Expanded the guide for 'Expand Your Project with External Packages from npm' * Added reference to semantic versioning in 'Add a Version to Your package.json' * fix/remove-links+fix-solutions * fix/remove-more-links
886 B
886 B
title
title |
---|
Expand Your Project with External Packages from npm |
Expand Your Project with External Packages from npm
The package.json
file in the root directory of your project, among other things, lists all the dependencies that your project needs in order to work, are listed under the dependencies
key in that file and follow a similar convention as given below:
"dependencies": {
"express": "^4.16.4",
"helmet": "^3.14.0"
},
There might be additional peer dependencies or development dependencies that your project might need in case it has to be built or compiled due to a number of reasons currently outside the scope of this challenge. They are listed under the peerDependecies
and devDependencies
respectively.