Server IP : 127.0.0.2 / Your IP : 3.143.111.52 Web Server : Apache/2.4.18 (Ubuntu) System : User : www-data ( ) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : disk_free_space,disk_total_space,diskfreespace,dl,exec,fpaththru,getmyuid,getmypid,highlight_file,ignore_user_abord,leak,listen,link,opcache_get_configuration,opcache_get_status,passthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,php_uname,phpinfo,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwnam,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,pclose,popen,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,shell_exec,source,show_source,system,virtual MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/npm/doc/cli/ |
Upload File : |
npm-tag(1) -- Tag a published version ===================================== ## SYNOPSIS [DEPRECATED] npm tag <name>@<version> [<tag>] See `dist-tag` ## DESCRIPTION THIS COMMAND IS DEPRECATED. See npm-dist-tag(1) for details. Tags the specified version of the package with the specified tag, or the `--tag` config if not specified. A tag can be used when installing packages as a reference to a version instead of using a specific version number: npm install <name>@<tag> When installing dependencies, a preferred tagged version may be specified: npm install --tag <tag> This also applies to `npm dedupe`. Publishing a package always sets the "latest" tag to the published version. ## PURPOSE Tags can be used to provide an alias instead of version numbers. For example, `npm` currently uses the tag "next" to identify the upcoming version, and the tag "latest" to identify the current version. A project might choose to have multiple streams of development, e.g., "stable", "canary". ## CAVEATS Tags must share a namespace with version numbers, because they are specified in the same slot: `npm install <pkg>@<version>` vs `npm install <pkg>@<tag>`. Tags that can be interpreted as valid semver ranges will be rejected. For example, `v1.4` cannot be used as a tag, because it is interpreted by semver as `>=1.4.0 <1.5.0`. See <https://github.com/npm/npm/issues/6082>. The simplest way to avoid semver problems with tags is to use tags that do not begin with a number or the letter `v`. ## SEE ALSO * npm-publish(1) * npm-install(1) * npm-dedupe(1) * npm-registry(7) * npm-config(1) * npm-config(7) * npm-tag(3) * npmrc(5)