npm-install-ci-test

Install dependencies and run tests

$ npm [[cit|install-ci-test]]

$ npm [[cit|install-ci-test]] --verbose

npm-install-ci-test [<npm-ci-options>] [-- <npm-test-options>]

This conceptual command typically represents the execution of:
npm ci [<options>] && npm test [<options>]

--prefix
    
(Applicable to `npm ci` and `npm test`)
The folder in which to look for a `package.json` file. Defaults to the current working directory.

--loglevel
    
(Applicable to `npm ci` and `npm test`)
What level of logs to output. Possible values: `silent`, `error`, `warn`, `info`, `http`, `verbose`, `silly`.

--json
    
(Applicable to `npm test`)
Outputs test results in JSON format, useful for programmatic consumption in CI systems.

--no-audit
    
(Applicable to `npm ci`)
Disables the audit step when installing dependencies. This can speed up installation but bypasses security checks.

--ignore-scripts
    
(Applicable to `npm ci` and `npm test`)
Disables the execution of `pre/post` scripts defined in `package.json`. Useful for security or performance in specific CI scenarios.

--force
    
(Applicable to `npm ci`)
Forces the installation of dependencies, even if `package-lock.json` is missing or corrupted. Generally not recommended for CI due to potential inconsistencies.

The `npm-install-ci-test` command represents a common pattern or custom script used primarily in Continuous Integration (CI) and Continuous Delivery (CD) environments for Node.js projects. Its core function is to first ensure that all project dependencies are installed in a clean and consistent manner, and then to execute the project's defined test suite. While not a standalone command shipped with `npm` itself, it encapsulates the crucial steps of setting up a build environment for a Node.js application and verifying its functionality.

The "ci" in its name emphasizes the use of `npm ci` for dependency installation, which is optimized for CI environments to provide speed, consistency, and reliability by strictly adhering to the `package-lock.json` or `npm-shrinkwrap.json` file. Following a successful installation, `npm-install-ci-test` proceeds to run the `npm test` command, which executes the scripts defined under the "test" property in the project's `package.json` file. This sequence is fundamental for automated quality assurance, ensuring that any new code changes or deployments do not introduce regressions and that the application remains functional.

• `package-lock.json` Requirement: `npm ci` requires a `package-lock.json` or `npm-shrinkwrap.json` file to be present. If it's missing, `npm ci` will fail, ensuring consistent installs.
• Clean State: `npm ci` removes any existing `node_modules` directory before installing. This ensures a clean slate, but can be slower if `node_modules` already contains necessary packages from a previous run (though this is typically desired in CI).
• Network Dependency: Both `npm ci` and `npm test` (if tests involve network requests or external resources) depend on network connectivity to fetch packages or external data.
• Resource Usage: Running tests can be CPU and memory intensive, especially for large projects, potentially impacting build agent performance in CI.
• Test Flakiness: Tests themselves can be flaky, leading to intermittent failures not caused by code changes. `npm-install-ci-test` will report these as failures.

While `npm install` is commonly used for local development, `npm ci` (clean install) is the recommended command for CI environments.

npm install: Installs dependencies from `package.json`, updating `package-lock.json` if necessary. It attempts to resolve new compatible versions if `package-lock.json` is outdated or missing. It reuses existing `node_modules` if possible.

npm ci: Strictly installs dependencies exactly as specified in `package-lock.json`. It requires `package-lock.json` to exist, and it deletes `node_modules` before installing to ensure a fresh, consistent environment. It's faster for repeat installs and ensures identical dependency trees across environments.

The `npm-install-ci-test` pattern emerged with the increasing adoption of Continuous Integration and the need for reliable and reproducible builds in Node.js projects. Prior to `npm ci`, developers often used `npm install` in CI, which could lead to inconsistencies if `package-lock.json` wasn't strictly honored or if `node_modules` wasn't cleaned properly. The introduction of `npm ci` in `npm` version 5.7.0 (January 2018) specifically addressed these CI challenges, providing a faster, more consistent, and more reliable way to install dependencies. This led to the formalization of the `npm ci && npm test` sequence, often encapsulated in custom scripts or CI pipeline configurations, effectively giving rise to the "npm-install-ci-test" concept as a best practice for automated project validation.

npm(1), npm-ci(1), npm-test(1), package.json(5)