npm publish (which uploads packages to the npm registry).Npm runs life cycle scripts during npm commands such as: This is what happens if we run hello: % npm -s run hello Npm package scripts are defined via property 'scripts' of package.json: This chapter explains them and how we can write them so that they work on both Windows and Unixes (macOS, Linux, etc.).

Package.json has the property 'scripts' which lets us define package scripts, small shell scripts that perform package-related tasks such as compiling artifacts or running tests.

15.9.2 Defining operating-system-specific scripts.

15.9.1 per-env: switching between scripts, depending on $NODE_ENV.

15.9 Expanding the capabilities of package scripts.

15.8.4 Putting files or directories into the trash.

15.8.2 Running multiple scripts concurrently or sequentially.

15.8.1 Running package scripts from a command line.

15.8 Helper packages for common operations.

15.7.6 Running bin scripts and package-internal modules.

15.7.5 Commands that work on both platforms.

15.7.4 Piping and redirecting input and output.

15.7.3 The exit codes of package scripts.

15.6.5 Observations of how npm logging works.

15.6.4 Output of life cycle scripts that run during npm install.

15.6.2 Log levels and information written to the npm log.

15.6.1 Log levels and information printed to the terminal.

15.6 The npm log level (how much output is produced).

15.4.2 Setting up environment variables via.

15.4.1 Getting and setting environment variables.15.4 Using environment variables in package scripts.

15.3 The shell environment in which package scripts are run.

15.1.5 Listing and organizing package scripts.

15.1.4 Getting tab completion for package scripts on Unix.

15.1.3 Preventing package scripts from being run automatically.

15.1.2 Which shell is used to run package scripts?.

15.1.1 Shorter npm commands for running package scripts.

Npm config set loglevel http