3.2 nrm安装-CSDN博客

本文链接：https://blog.csdn.net/LetsStudy/article/details/118575729

本文档介绍了如何解决在使用nrm（npm registry manager）时遇到的TypeError报错，通过修改nrm的cli.js文件来适配不同平台。同时，提供了nrm的基本用法，包括列出所有注册表、切换注册表、查看当前注册表等操作。此外，还展示了如何检查和更改npm源。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

一、npm全局安装nrm

npm install nrm -g

二、cmd运行nrm

如果出现如下报错

node:internal/validators:119
    throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
    ^

[TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

修改C:\Users\javain\AppData\Roaming\nvm\v16.4.1\node_modules\nrm目录下cli.js


//删除原码中const NRMRC = path.join(process.env.HOME, '.nrmrc'); 替换为下面的代码
const NRMRC = path.join(process.env[(process.platform == 'win32') ? 'USERPROFILE' : 'HOME'], '.nrmrc');

找不到目录可以在Roaming搜索一下

三、使用

Usage: nrm [options] [command]

  Commands:

    ls                                    List all the registries
    current                               Show current registry name
    use <registry>                        Change registry to registry
    add <registry> <url> [home]           Add one custom registry
    login <registry> [value]              Set authorize information for a registry with a base64 encoded string or username and pasword
      -a  --always-auth                     Set is always auth
      -u  --username <username>             Your user name for this registry
      -p  --password <password>             Your password for this registry
      -e  --email <email>                   Your email for this registry
    set-hosted-repo <registry> <value>    Set hosted npm repository for a custom registry to publish packages
    set-scope <scopeName> <value>         Associating a scope with a registry
    del-scope <scopeName>                 Remove a scope
    set <registryName>                    Set custom registry attribute
      -a  --attr <attr>                    Set custorm registry attribute
      -v  --value <value>                  Set custorm registry value
    del <registry>                        Delete one custom registry
    rename <registryName> <newName>       Set custom registry name
    home <registry> [browser]             Open the homepage of registry with optional browser
    publish [<tarball>|<folder>]          Publish package to current registry if current registry is a custom registry. The field 'repository' of current custom registry is required running this command. If you're not using custom registry, this command will run npm publish directly
      -t  --tag [tag]                        Add tag
      -a  --access <public|restricted>       Set access
      -o  --otp [otpcode]                    Set otpcode
      -dr --dry-run                          Set is dry run
    test [registry]                       Show the response time for one or all registries
    help                                  Print this help

  Options:

    -h  --help     output usage information
    -V  --version  output the version number