UNPKG

trainingproject

Version:

A module to teach you how to module.

github.com/npm/how-to-npm

npm/how-to-npm

17 lines (12 loc) • 731 B
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Every published package on npm has a `dist-tags` entry on it which maps strings like "latest" to version numbers like "1.2.48". By default, the "latest" version is what gets installed. When you publish, the version that you publish gets tagged as "latest". This is generally great, because most of the time you publish things when you're ready for users to use them. However, if you need to publish something, and *not* make it the default version of a package (for example, if it's a security release for a legacy version, or something), then you can manually manage these distribution tags with the `dist-tag` function. Run `npm help dist-tag` to learn more about it. Try adding a dist-tag on your package.