- Updated dependencies [ee429b300]
- @pnpm/cli-utils@2.0.8
- @pnpm/cli-utils@2.0.7
- @pnpm/cli-utils@2.0.6
- @pnpm/cli-utils@2.0.5
- @pnpm/cli-utils@2.0.4
- @pnpm/cli-utils@2.0.3
- @pnpm/cli-utils@2.0.2
- @pnpm/cli-utils@2.0.1
- eceaa8b8b: Node.js 14 support dropped.
- Updated dependencies [eceaa8b8b]
- @pnpm/cli-utils@2.0.0
- @pnpm/cli-utils@1.1.7
- @pnpm/cli-utils@1.1.6
- @pnpm/cli-utils@1.1.5
- @pnpm/cli-utils@1.1.4
- @pnpm/cli-utils@1.1.3
-
d80661d42: The configuration added by
pnpm setup
should check if the pnpm home directory is already in the PATH before adding to the PATH.Before this change, this code was added to the shell:
export PNPM_HOME="$HOME/Library/pnpm" export PATH="$PNPM_HOME:$PATH"
Now this will be added:
export PNPM_HOME="$HOME/Library/pnpm" case ":$PATH:" in *":$PNPM_HOME:"*) ;; *) export PATH="$PNPM_HOME:$PATH" ;; esac
-
Updated dependencies [7d64d757b]
- @pnpm/cli-utils@1.1.2
- @pnpm/cli-utils@1.1.1
- Updated dependencies [0377d9367]
- @pnpm/cli-utils@1.1.0
- @pnpm/cli-utils@1.0.34
- @pnpm/cli-utils@1.0.33
- @pnpm/cli-utils@1.0.32
- @pnpm/cli-utils@1.0.31
- @pnpm/cli-utils@1.0.30
- @pnpm/cli-utils@1.0.29
- @pnpm/cli-utils@1.0.28
- @pnpm/cli-utils@1.0.27
- @pnpm/cli-utils@1.0.26
- @pnpm/cli-utils@1.0.25
- @pnpm/cli-utils@1.0.24
- @pnpm/cli-utils@1.0.23
- @pnpm/cli-utils@1.0.22
- @pnpm/cli-utils@1.0.21
- @pnpm/cli-utils@1.0.20
- @pnpm/cli-utils@1.0.19
- @pnpm/cli-utils@1.0.18
- @pnpm/cli-utils@1.0.17
- @pnpm/cli-utils@1.0.16
- @pnpm/cli-utils@1.0.15
- @pnpm/cli-utils@1.0.14
- @pnpm/cli-utils@1.0.13
- @pnpm/cli-utils@1.0.12
- @pnpm/cli-utils@1.0.11
- @pnpm/cli-utils@1.0.10
- @pnpm/cli-utils@1.0.9
- @pnpm/cli-utils@1.0.8
- @pnpm/cli-utils@1.0.7
- @pnpm/cli-utils@1.0.6
- @pnpm/cli-utils@1.0.5
- @pnpm/cli-utils@1.0.4
- @pnpm/cli-utils@1.0.3
- @pnpm/cli-utils@1.0.2
- @pnpm/cli-utils@1.0.1
- f884689e0: Require
@pnpm/logger
v5.
- Updated dependencies [f884689e0]
- @pnpm/cli-utils@1.0.0
- @pnpm/cli-utils@0.7.43
- @pnpm/cli-utils@0.7.42
- @pnpm/cli-utils@0.7.41
- @pnpm/cli-utils@0.7.40
- @pnpm/cli-utils@0.7.39
- @pnpm/cli-utils@0.7.38
- @pnpm/cli-utils@0.7.37
- @pnpm/cli-utils@0.7.36
- @pnpm/cli-utils@0.7.35
- @pnpm/cli-utils@0.7.34
- @pnpm/cli-utils@0.7.33
- @pnpm/cli-utils@0.7.32
- @pnpm/cli-utils@0.7.31
- @pnpm/cli-utils@0.7.30
- @pnpm/cli-utils@0.7.29
- @pnpm/cli-utils@0.7.28
- 8cb47ac9d:
pnpm setup
: don't usesetx
to set env variables on Windows.- @pnpm/cli-utils@0.7.27
- fe53c2986: On POSIX
pnpm setup
should suggest users to source the config instead of restarting the terminal.
- @pnpm/cli-utils@0.7.26
- @pnpm/cli-utils@0.7.25
- @pnpm/cli-utils@0.7.24
- @pnpm/cli-utils@0.7.23
- @pnpm/cli-utils@0.7.22
- @pnpm/cli-utils@0.7.21
- @pnpm/cli-utils@0.7.20
- @pnpm/cli-utils@0.7.19
- @pnpm/cli-utils@0.7.18
- Updated dependencies [5f643f23b]
- @pnpm/cli-utils@0.7.17
- @pnpm/cli-utils@0.7.16
- @pnpm/cli-utils@0.7.15
- @pnpm/cli-utils@0.7.14
- @pnpm/cli-utils@0.7.13
- @pnpm/cli-utils@0.7.12
- @pnpm/cli-utils@0.7.11
- @pnpm/cli-utils@0.7.10
- @pnpm/cli-utils@0.7.9
- @pnpm/cli-utils@0.7.8
- @pnpm/cli-utils@0.7.7
- e6a9f157d:
pnpm setup
should not fail on Windows ifPNPM_HOME
is not yet in the system registry #4757
- @pnpm/cli-utils@0.7.6
- 71c7ed998:
pnpm setup
should update the config of the current shell, not the preferred shell. - 460ccf60e: fix: make
pnpm setup
free of garbled characters. - 61d102a99:
pnpm setup
should not override the PNPM_HOME env variable on Windows, unless--force
is used. - 7c9362d3d: fix
pnpm setup
breaks %PATH% with non-ascii characters #4698 - Updated dependencies [52b0576af]
- @pnpm/cli-utils@0.7.5
- @pnpm/cli-utils@0.7.4
- @pnpm/cli-utils@0.7.3
- @pnpm/cli-utils@0.7.2
- @pnpm/cli-utils@0.7.1
- 542014839: Node.js 12 is not supported.
- Updated dependencies [542014839]
- @pnpm/cli-utils@0.7.0
- @pnpm/cli-utils@0.6.50
- @pnpm/cli-utils@0.6.49
- @pnpm/cli-utils@0.6.48
- @pnpm/cli-utils@0.6.47
- @pnpm/cli-utils@0.6.46
- @pnpm/cli-utils@0.6.45
- @pnpm/cli-utils@0.6.44
- @pnpm/cli-utils@0.6.43
- @pnpm/cli-utils@0.6.42
- @pnpm/cli-utils@0.6.41
- @pnpm/cli-utils@0.6.40
- @pnpm/cli-utils@0.6.39
- @pnpm/cli-utils@0.6.38
- @pnpm/cli-utils@0.6.37
- @pnpm/cli-utils@0.6.36
- @pnpm/cli-utils@0.6.35
- @pnpm/cli-utils@0.6.34
- @pnpm/cli-utils@0.6.33
- b847e0300:
pnpm setup
should create shell rc files for pnpm path configuration if no such file exists prior #4027.
- @pnpm/cli-utils@0.6.32
- @pnpm/cli-utils@0.6.31
- @pnpm/cli-utils@0.6.30
- @pnpm/cli-utils@0.6.29
- @pnpm/cli-utils@0.6.28
- @pnpm/cli-utils@0.6.27
- @pnpm/cli-utils@0.6.26
- @pnpm/cli-utils@0.6.25
- @pnpm/cli-utils@0.6.24
- @pnpm/cli-utils@0.6.23
- @pnpm/cli-utils@0.6.22
- 04b7f6086: Use safe-execa instead of execa to prevent binary planting attacks on Windows.
- @pnpm/cli-utils@0.6.21
- @pnpm/cli-utils@0.6.20
- cee8b73f1: Set
PATH
environment variable toPNPM_HOME
on Win32 platform
- @pnpm/cli-utils@0.6.19
- ade0fa92f: The original binary will not be removed after pnpm setup.
- @pnpm/cli-utils@0.6.18
- 71cc21832: Print info message about the requirement to open a new terminal.
- @pnpm/cli-utils@0.6.17
- 8d038f8f1: pnpm setup moves the CLI to the pnpm home directory.
- @pnpm/cli-utils@0.6.16
- @pnpm/cli-utils@0.6.15
- @pnpm/cli-utils@0.6.14
- @pnpm/cli-utils@0.6.13
- @pnpm/cli-utils@0.6.12
- @pnpm/cli-utils@0.6.11
- @pnpm/cli-utils@0.6.10
- @pnpm/cli-utils@0.6.9
- @pnpm/cli-utils@0.6.8
- 6a64c1ff5: A summary should be printed.
- @pnpm/cli-utils@0.6.7
- @pnpm/cli-utils@0.6.6
- 473223be9: Project created.
- @pnpm/cli-utils@0.6.5