NPM-TAG(3)

πŸ“¦ version 1.2.1, in nixos 26.05, nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, this is npm-tag β€” the NPM-TAG(3) manual page β€” and it is literally here to tag a published version. periodt. πŸŽ€


✨ SYNOPSIS ✨

npm.commands.tag(package@version, tag, callback)

πŸ¦‹ DESCRIPTION πŸ¦‹

It tags the specified version of the package with the specified tag, or the --tag config if not specified. slay. πŸ’–

A few little deets, because we love clarity:

  • The 'package@version' is an array of strings, but only the first two elements are currently used. no cap.
  • The first element must be in the form package@version, where package is the package name and version is the version number (much like installing a specific version). iconic behavior, honestly. 🌈
  • The second element is the name of the tag to tag this version with.
  • If this parameter is missing or falsey (empty), the default from the config will be used. 🫢
  • For more information about how to set this config, check man 3 npm-config for programmatic usage or man npm-config for cli usage. iykyk. πŸ”₯
bestie, that's the whole vibe: package version + tag name, and the config default steps in when the tag is missing or falsey. πŸ’…

mwah πŸ’‹ β€” signing off from March 2017, with the NPM-TAG(3) footer energy. πŸ¦‹βœ¨

πŸ“¦ where this page comes from