Node.js + パッケージマネージャ：NPM, Yarn

[tk-fuse]

npm

About npm | npm Docs

package.json にリストアップされる各パッケージのバージョン表記ルール

GitHub - npm/node-semver: The semver parser for node (the one npm uses)

Advanced Range Syntax

Advanced range syntax desugars to primitive comparators in deterministic ways.

Advanced ranges may be combined in the same way as primitive comparators using white space or ||.

Hyphen Ranges X.Y.Z - A.B.C

Specifies an inclusive set.

• 1.2.3 - 2.3.4 := >=1.2.3 <=2.3.4

If a partial version is provided as the first version in the inclusive range, then the missing pieces are replaced with zeroes.

• 1.2 - 2.3.4 := >=1.2.0 <=2.3.4

If a partial version is provided as the second version in the inclusive range, then all versions that start with the supplied parts of the tuple are accepted, but nothing that would be greater than the provided tuple parts.

• 1.2.3 - 2.3 := >=1.2.3 <2.4.0-0
• 1.2.3 - 2 := >=1.2.3 <3.0.0-0

X-Ranges 1.2.x 1.X 1.2.* *

Any of X, x, or * may be used to “stand in” for one of the numeric values in the [major, minor, patch] tuple.

• * := >=0.0.0 (Any non-prerelease version satisfies, unless includePrerelease is specified, in which case any version at all satisfies)
• 1.x := >=1.0.0 <2.0.0-0 (Matching major version)
• 1.2.x := >=1.2.0 <1.3.0-0 (Matching major and minor versions)

A partial version range is treated as an X-Range, so the special character is in fact optional.

• "" (empty string) := * := >=0.0.0
• 1 := 1.x.x := >=1.0.0 <2.0.0-0
• 1.2 := 1.2.x := >=1.2.0 <1.3.0-0

Tilde Ranges ~1.2.3 ~1.2 ~1

Allows patch-level changes if a minor version is specified on the comparator. Allows minor-level changes if not.

• ~1.2.3 := >=1.2.3 <1.(2+1).0 := >=1.2.3 <1.3.0-0
• ~1.2 := >=1.2.0 <1.(2+1).0 := >=1.2.0 <1.3.0-0 (Same as 1.2.x)
• ~1 := >=1.0.0 <(1+1).0.0 := >=1.0.0 <2.0.0-0 (Same as 1.x)
• ~0.2.3 := >=0.2.3 <0.(2+1).0 := >=0.2.3 <0.3.0-0
• ~0.2 := >=0.2.0 <0.(2+1).0 := >=0.2.0 <0.3.0-0 (Same as 0.2.x)
• ~0 := >=0.0.0 <(0+1).0.0 := >=0.0.0 <1.0.0-0 (Same as 0.x)
• ~1.2.3-beta.2 := >=1.2.3-beta.2 <1.3.0-0 Note that prereleases in the 1.2.3 version will be allowed, if they are greater than or equal to beta.2. So, 1.2.3-beta.4 would be allowed, but 1.2.4-beta.2 would not, because it is a prerelease of a different [major, minor, patch] tuple.

Caret Ranges ^1.2.3 ^0.2.5 ^0.0.4

Allows changes that do not modify the left-most non-zero element in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.

Many authors treat a 0.x version as if the x were the major “breaking-change” indicator.

Caret ranges are ideal when an author may make breaking changes between 0.2.4 and 0.3.0 releases, which is a common practice. However, it presumes that there will not be breaking changes between 0.2.4 and 0.2.5. It allows for changes that are presumed to be additive (but non-breaking), according to commonly observed practices.

• ^1.2.3 := >=1.2.3 <2.0.0-0
• ^0.2.3 := >=0.2.3 <0.3.0-0
• ^0.0.3 := >=0.0.3 <0.0.4-0
• ^1.2.3-beta.2 := >=1.2.3-beta.2 <2.0.0-0 Note that prereleases in the 1.2.3 version will be allowed, if they are greater than or equal to beta.2. So, 1.2.3-beta.4 would be allowed, but 1.2.4-beta.2 would not, because it is a prerelease of a different [major, minor, patch] tuple.
• ^0.0.3-beta := >=0.0.3-beta <0.0.4-0 Note that prereleases in the 0.0.3 version only will be allowed, if they are greater than or equal to beta. So, 0.0.3-pr.2 would be allowed.

When parsing caret ranges, a missing patch value desugars to the number 0, but will allow flexibility within that value, even if the major and minor versions are both 0.

• ^1.2.x := >=1.2.0 <2.0.0-0
• ^0.0.x := >=0.0.0 <0.1.0-0
• ^0.0 := >=0.0.0 <0.1.0-0

A missing minor and patch values will desugar to zero, but also allow flexibility within those values, even if the major version is zero.

• ^1.x := >=1.0.0 <2.0.0-0
• ^0.x := >=0.0.0 <1.0.0-0

Range Grammar

Putting all this together, here is a Backus-Naur grammar for ranges, for the benefit of parser authors:

range-set  ::= range ( logical-or range ) *
logical-or ::= ( ' ' ) * '||' ( ' ' ) *
range      ::= hyphen | simple ( ' ' simple ) * | ''
hyphen     ::= partial ' - ' partial
simple     ::= primitive | partial | tilde | caret
primitive  ::= ( '<' | '>' | '>=' | '<=' | '=' ) partial
partial    ::= xr ( '.' xr ( '.' xr qualifier ? )? )?
xr         ::= 'x' | 'X' | '*' | nr
nr         ::= '0' | ['1'-'9'] ( ['0'-'9'] ) *
tilde      ::= '~' partial
caret      ::= '^' partial
qualifier  ::= ( '-' pre )? ( '+' build )?
pre        ::= parts
build      ::= parts
parts      ::= part ( '.' part ) *
part       ::= nr | [-0-9A-Za-z]+

[tk-fuse]

パッケージマネージャからNode.js, npmをインストール

Node.js — Installing Node.js via package manager

GitHub - nodesource/distributions: NodeSource Node.js Binary Distributions

Node.js v21.x:

Using Ubuntu

$ curl -fsSL https://deb.nodesource.com/setup_21.x | sudo -E bash - && sudo apt-get install -y nodejs

Using Debian, as root

# curl -fsSL https://deb.nodesource.com/setup_21.x | bash - && apt-get install -y nodejs

nvm(Node Version Manager)によるローカルインストール

ユーザディレクトリで異なるバージョンのNodeを実行可。

GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to...

$ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

$ nvm ls-remote
.....
.....
       v18.18.2   (LTS: Hydrogen)
       v18.19.0   (Latest LTS: Hydrogen)
       v19.0.0
.....
.....
       v20.9.0   (LTS: Iron)
       v20.10.0   (LTS: Iron)
       v20.11.0   (Latest LTS: Iron)
.....
.....

バージョンを指定してインストール

$ nvm install 18.18.2 # or 20.11.0, 19.0.0, etc

インストールした最新版を指定

$ nvm use node
Now using node v20.11.0 (npm v10.2.4)

バージョンの変更

$ nvm use 16.20.1
Now using node v16.20.1 (npm v8.19.4)

デフォルトバージョンの変更
注）インストール時に–defaultオプションを指定しない場合に必要な処置です。

$ nvm alias default 20.11.0

パッケージのインストール（グローバルオプション [-g|–global] を指定）

$ npm install -g yarn

Docker

DockerHub
Docker

GitHub

GitHub - nodejs/docker-node: Official Docker Image for Node.js :turtle:

---

Node.js, the difference between development and production

Node.js — Node.js, the difference between development and production

---

バージョンスケジュール

Node.js — Previous Releases

[tk-fuse]

パッケージマネージャ：Yarn

Home page | Yarn

NPMとYarnとの比較

Yarn vs NPM: Which package manager should I use?

Action	NPM Command	Yarn Command
Initialize project	npm init	yarn init
Run script	npm run	yarn run
Run tests	npm test	yarn test
Install dependencies	npm install	yarn
Install packages	npm install	yarn add
Uninstall packages	npm uninstall	yarn remove
Install packages globally	npm install -g	yarn global add
Uninstall packages globally	npm uninstall -g	yarn global remove
Update packages	npm update	yarn upgrade
Interactive dependency update	npm run upgrade-interactive	yarn upgrade-interactive
Check for outdated packages	npm outdated	yarn outdated
Manage local cache	npm cache clean	yarn cache clean
Login/Logout	npm login/logout	yarn login/logout
Publish package	npm publish	yarn publish
Update package manager	npm update	yarn upgrade
Run package remotely	Not Supported (but npx)	yarn dlx
Check licenses	Not Supported	yarn licenses ls

インストール

# npm install --global yarn
# yarn --version
1.22.21