Log in Sign up
Public npm registry for reliable package access

Install npm packages through a stable, familiar registry endpoint

Package installation should not stop when direct registry access becomes limited or unstable. Configure the public FluxCDN endpoint once, then keep using npm install and npm ci across projects, servers, CI/CD jobs, and Docker builds.

See everyday commands Enable the npm registry
Package delivery route availablenpm.fluxcdn.cloud
Official npm registryOriginal public packages
FluxCDNA secure, available route
Project or serverStandard npm commands
expresslatest nextlatest @types/nodepublic npm install

Public HTTPS registrynpm.fluxcdn.cloud

No account requiredDownload public packages without signing in

Works with npm install and npm ciKeep your current install workflow

Public scoped packagesIncluding @types/node

Use a dependable route to public npm packages

Package names, versions, and install commands remain familiar. FluxCDN retrieves public package data and files from the official npm registry.

  • Sourced from the official npm registryPublic package metadata and tarballs originate from the official npm registry.
  • Regular and public scoped packagesUse the same package names and versions your project already expects.
  • A public download endpointPublishing is disabled; this service is intended for installing public packages.

Enable the npm registry at the scope you need

Choose a project-only setting, a user-wide setting, or one command without changing your defaults.

Configure one project

Add this line to .npmrc in the project root. Your user-wide npm configuration stays unchanged.

registry=https://npm.fluxcdn.cloud/

Verify the active registryThe output should be https://npm.fluxcdn.cloud/.

npm config get registry

Keep using npm as usual

There is no need to change package.json, package names, or installation commands. npm reads the registry from your active configuration.

  • Install project dependenciesnpm install retrieves the packages declared in package.json.
  • Public scoped packagesPackages such as @types/node install under their normal names.
  • Clean lockfile-based installsnpm ci remains unchanged for servers and deployment workflows.
Ready-to-use commands
npm install
npm install express
npm install @types/node
npm ci
Dependencies install into the familiar project structure.node_modules/

Bring the npm registry into deployment workflows

Choose a ready example for CI/CD, Docker builds, or package inspection. Each example works independently.

Install dependencies in CI/CD

Configure the registry before npm ci so package-lock.json keeps controlling exact versions.

npm config set registry https://npm.fluxcdn.cloud/
npm ci

The access boundary is explicit

This endpoint downloads public npm packages. No FluxCDN account is required, and publishing to the public registry is disabled.

Return to the official npm registryRestore your user-wide setting with this command whenever needed.

npm config set registry https://registry.npmjs.org/
Download public packagesSupported
Read package versions and metadataSupported
Download public scoped packagesSupported
Publish packagesDisabled

If an install fails, begin with these three checks

Confirm the active registry, test the endpoint response, then request metadata for one public package.

1

Check the active registry addressnpm config get registry

2

Confirm the registry returns PONGnpm ping --registry=https://npm.fluxcdn.cloud/

3

Check access to package metadatanpm view lodash version --registry=https://npm.fluxcdn.cloud/

npm Registry questions

Short answers for configuration scope, everyday use, and restoring the official registry.

Do I need a FluxCDN account to download packages?

No. Public packages can be downloaded from npm.fluxcdn.cloud without an account or sign-in.

Are scoped packages supported?

Yes. Public scoped packages such as @types/node work with the usual npm install command.

How do I see which registry npm is using?

Run npm config get registry. When FluxCDN is active, it should show https://npm.fluxcdn.cloud/.

How do I limit the setting to one project?

Create .npmrc in that project root and add registry=https://npm.fluxcdn.cloud/.

Can I publish my own package to this registry?

No. The public FluxCDN registry is intended for package downloads, and publishing is disabled.

How do I return to the official npm registry?

Run npm config set registry https://registry.npmjs.org/, then verify the result with npm config get registry.

FluxCDN

Enable the npm registry for your next project

Choose the right scope, copy the ready configuration, and keep installing dependencies with familiar commands.

Choose a setup methodView Linux repositories