NPM Registry

A cleaner registry path for npm, pnpm, yarn and CI installs

Package install delays may look small, but they repeat across laptops, CI runners and image builds. npm.bounera.com is meant to control that layer more clearly.

npmpnpmyarnnpm.bounera.com

Ops view

NPM Registry

npm mirror

Where it fits best

Laptop onboarding, monorepo installs, Node.js image builds and daily JS or TS pipelines.

Faster installs are not the whole story

A clear registry path inside `.npmrc` and CI also makes dependency flow more legible for the team.

Service host

npm.bounera.com

Ecosystemnpm.bounera.com

npmpnpmyarnworkspace

Quick start

For the fastest start, point the global registry at Bounera and run a real install.

npm

bash

Ready command

Verified path

npm config set registry https://npm.bounera.com/ && npm install

pnpm

pnpm config set registry https://npm.bounera.com/ && pnpm install

yarn

yarn config set npmRegistryServer https://npm.bounera.com/ && yarn install

Manual setup for projects, CI and corepack

For team repositories, place the registry inside project files or automation so local onboarding and CI use the same مسیر وابستگی.

Project-level .npmrc

ini

Ready command

Verified path

registry=https://npm.bounera.com/
strict-ssl=true
fetch-retries=5
fetch-timeout=120000

pnpm bootstrap

bash

Ready command

Verified path

corepack enable && pnpm config set registry https://npm.bounera.com/ && pnpm install --frozen-lockfile

Yarn Berry

yaml

Ready command

Verified path

npmRegistryServer: "https://npm.bounera.com/"
enableGlobalCache: true
checksumBehavior: "throw"

CI .npmrc injection

bash

Ready command

Verified path

printf 'registry=https://npm.bounera.com/\n' > .npmrc && npm ci

Verify and troubleshoot

Use `npm config get registry` or `pnpm config get registry` to verify the actual endpoint in use.
If you also use private scoped packages, review scope-specific config so it does not collide with the public registry path.
Compare `npm ci` or `pnpm install --frozen-lockfile` in CI before and after the change with the same cache conditions.

Controlled rollback

If the project uses `.npmrc`, rollback is usually just a revert of that file.
For machine-wide config, record the previous registry before changing it so reversions stay clean.
If only one scope is affected, rollback at the scope level instead of resetting the whole registry path.

Where the registry pays off most

Large monorepos

When dependency trees are heavy, a better registry improves both first installs and repeat syncs.

Ephemeral CI runners

Where runners do not keep a stable cache, registry quality becomes much more visible.

Node.js image builds

If every Docker build repeats dependency installation, the impact on build time becomes obvious.

Verify and troubleshoot

Use `npm config get registry` or `pnpm config get registry` to verify the actual endpoint in use.

If you also use private scoped packages, review scope-specific config so it does not collide with the public registry path.

Compare `npm ci` or `pnpm install --frozen-lockfile` in CI before and after the change with the same cache conditions.