npm Scripts: Automate Build, Test, Deploy Tasks (2026)

npm scripts are a surprisingly powerful, yet often underutilized, way to automate development workflows.

Let’s see how they work in practice with a simple Node.js project. Imagine you have a small web app that needs to be built (transpiled) and then tested.

Here’s a package.json file:

{
  "name": "my-web-app",
  "version": "1.0.0",
  "scripts": {
    "build": "babel src/index.js -o dist/bundle.js",
    "test": "jest",
    "start": "node dist/bundle.js",
    "dev": "npm run build && npm run start"
  },
  "devDependencies": {
    "@babel/cli": "^7.20.7",
    "@babel/core": "^7.20.12",
    "@babel/preset-env": "^7.20.2",
    "jest": "^29.3.1"
  }
}

In this package.json, the scripts section defines a set of commands you can run using npm run <script-name>.

"build": "babel src/index.js -o dist/bundle.js": This command uses Babel to transpile JavaScript code from src/index.js to dist/bundle.js.
"test": "jest": This command runs your tests using the Jest test runner.
"start": "node dist/bundle.js": This command executes the transpiled JavaScript file.
"dev": "npm run build && npm run start": This is a composite script. npm run build && npm run start means "first, run the build script, and if it succeeds, then run the start script."

To execute these, you’d open your terminal in the project’s root directory and type:

npm run build
npm run test
npm run start
npm run dev

This system solves the problem of repetitive, error-prone manual command execution. Instead of remembering the exact Babel flags or the Jest command, you have simple, memorable aliases. It standardizes how tasks are performed across a development team, ensuring everyone is using the same commands.

Internally, npm run simply looks up the script in your package.json and executes it within your project’s context. This means any binaries installed via npm (like babel or jest in this case) are automatically available in the PATH for that script’s execution. This avoids the need for global installations and keeps your project dependencies self-contained.

You can chain scripts together using shell operators like && (run next if successful) or || (run next if failed), or even run multiple npm scripts concurrently using packages like npm-run-all or concurrently. For example, to watch for file changes and rebuild automatically, you might add "watch": "babel src/index.js -o dist/bundle.js --watch" to your scripts.

The most surprising thing about npm scripts is how deeply they integrate with the npm ecosystem. You can define lifecycle scripts like preinstall, postinstall, prepublish, postpublish, pretest, posttest, etc. For example, a pretest script would run automatically before npm test. If pretest exits with a non-zero status code, npm test will be aborted. This allows for automated checks and setup before critical operations.

Beyond simple command execution, npm scripts can also leverage environment variables. You can pass variables to your scripts using the env command. For instance, you could have a script like "deploy:staging": "NODE_ENV=staging ./deploy.sh". This allows for conditional logic and configuration without modifying the script content itself, making your workflows more flexible and adaptable.

You can also use npm scripts to define dependencies between tasks. For example, if your deploy script relies on the build script completing successfully first, you can chain them: "deploy": "npm run build && ./scripts/deploy.sh". This ensures that your code is built before it’s deployed, preventing deployment of uncompiled or outdated assets.

The next step in automating your workflow is exploring how to manage cross-platform compatibility and more complex task orchestration.