Npm: beyond 'npm i'
0 likes578 views
NPM scripts allow developers to run predefined scripts at different stages of installing, publishing, and interacting with packages. These scripts are defined in the package.json file under the "scripts" key. Common script names include preinstall, install, postinstall, prepublish, publish, and postpublish. NPM versioning follows semantic versioning principles where versions are denoted as MAJOR.MINOR.PATCH. Dependencies can specify version ranges like tilde (~), caret (^), and hyphen (-) to control updates. Private NPM repositories and shrinkwrapping help ensure reproducible builds across environments. Scoped packages allow publishing packages under a unique namespace.
Npm: beyond 'npm i'
- 3. @piether
- 6. NPM?
- 7. NPM 2 vs NPM 3
- 11. NPM scripts
- 12. "scripts": { "postinstall": "echo "Thanks for installing my package "" },
- 13. ● prepublish: Run BEFORE the package is published. (Also run on local npm install without any arguments.) ● publish, postpublish: Run AFTER the package is published. ● preinstall: Run BEFORE the package is installed ● install, postinstall: Run AFTER the package is installed. ● preuninstall, uninstall: Run BEFORE the package is uninstalled. ● postuninstall: Run AFTER the package is uninstalled. ● preversion, version: Run BEFORE bump the package version. ● postversion: Run AFTER bump the package version. ● pretest, test, posttest: Run by the npm test command. ● prestop, stop, poststop: Run by the npm stop command. ● prestart, start, poststart: Run by the npm start command. ● prerestart, restart, postrestart: Run by the npm restart command. Note: npm restart will run the stop and start scripts if no restart script is provided. (https://docs.npmjs.com/misc/scripts) Predefined script names
- 14. "scripts": { "grunt-version" : "grunt --version" }, $ grunt --version grunt-cli v0.1.13 grunt v1.0.0 $ npm run grunt-version > [email protected] grunt /Users/pieter/projects/npm-test > grunt --version grunt-cli v1.2.0 grunt v1.0.1 Custom script names
- 15. How to use NPM as a build tool http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/
- 18. MAJOR.MINOR.PATCH = Semantic versioning aka semver
- 19. 1.2.3 - 2.3.4 Minimum version Comparator ( < or <= ) Maximum version
- 20. 1.2.3 - 2.3.4 1.2.3 <= 2.3.4 = Hyphen range
- 21. 1.x Minimum version Comparator ( < or <= ) Maximum version
- 22. 1.x 1.0.0 < 2.0.0 = Hyphen range
- 23. ~1.2.3 Minimum version Comparator ( < or <= ) Maximum version
- 24. ~1.2.3 1.2.3 < 1.3.0 = tilde range
- 25. ^1.2.3 Minimum version Comparator ( < or <= ) Maximum version
- 26. ^1.2.3 1.2.3 < 2.0.0 = caret range (default)
- 27. ^0.2.3 Minimum version Comparator ( < or <= ) Maximum version
- 29. NPM repositories
- 30. Module Module author: npm publish Your app You: npm install
- 31. March 23rd, 2016
- 34. babel leftpad
- 35. Module Module author: npm unpublish Your app You: npm install babel
- 38. You cannot publish over the previously published version.
- 41. ^0.0.3 Minimum version Comparator ( < or <= ) Maximum version
- 43. Module Module author: npm publish Your app You: npm install Private NPM repository
- 44. Module Module author: npm unpublish Your app You: npm install Private NPM repository
- 45. NPM shrinkwrap
- 48. $ npm shrinkwrap wrote npm-shrinkwrap.json
- 50. Your own NPM repo + shrinkwrap = reproducible builds :)
- 51. Scoped packages
- 52. Module @neoscores/some- module Your colleague: npm publish Your app You: npm login npm install @neoscores/some-module