@hutson/set-npm-auth-token-for-ci 4.0.2

Set authentication token placeholder into `.npmrc` file for use in automated CI processes.

@hutson/set-npm-auth-token-for-ci@4.0.2 was published on 2019-04-24. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.9.0.

Deprecated: This package is no longer maintained. If you would like to use the functionality offered by this package, please consider publishing a fork of this package under your own npm scope.

All @hutson/set-npm-auth-token-for-ci versions · Permanent reference to 4.0.2 · Latest release

Package specifications

Version4.0.2
License declarationApache-2.0
Published2019-04-24T20:56:21.398Z
Node.js requirement>=8.9.0
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size22.48 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies18
Repository starsUnknown
Repository forksUnknown

Install @hutson/set-npm-auth-token-for-ci 4.0.2

npm install @hutson/set-npm-auth-token-for-ci@4.0.2
pnpm add @hutson/set-npm-auth-token-for-ci@4.0.2
yarn add @hutson/set-npm-auth-token-for-ci@4.0.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness