Generate .npmrc configuration files instantly. Configure npm registry, scoped packages, auth tokens, save behavior, and more. All processing happens client-side — no data is sent to any server.
For security, tokens are included as placeholders. Replace with your actual credentials before using.
.npmrc is the configuration file for npm, the world's largest software registry. It controls how npm installs packages, which registry to use, authentication credentials, and various behavioral settings. This generator creates properly formatted .npmrc files for common development scenarios — from simple registry switches to complex multi-scope enterprise configurations. All generation happens entirely in your browser for maximum security.
.npmrc is npm's configuration file. You can place it in your project root (per-project config), in your home directory ~/.npmrc (per-user config), or use the npm config command. Project-level .npmrc is committed to git and shared with your team.
Scoped registries let you route packages with a specific scope (like @mycompany) to a different registry. For example, @mycompany packages can come from your private registry while everything else comes from npm. This is essential for enterprise development.
Yes for project-level .npmrc that contains registry URLs and non-sensitive settings. However, never commit files containing real auth tokens or passwords. Use environment variables or CI/CD secrets for authentication.
save-exact=true saves exact versions without any prefix (e.g., "1.2.3"). save-prefix controls the default prefix when save-exact is false — "^" allows minor/patch updates, "~" allows only patch updates. Exact versions give reproducible builds.