Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] npm ci wipes out the scripts in the .bin folder and does not replace them #4035

Closed
2 tasks done
wandyezj opened this issue Nov 10, 2021 · 1 comment
Closed
2 tasks done
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release

Comments

@wandyezj
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

npm ci wipes out scripts in the .bin folder instead of reinstalling them.

Expected Behavior

npm ci reinstalls .bin scripts for each package

Steps To Reproduce

Use the npm version that comes with Node LTS this is NPM 8.1

  1. npm install --save-dev prettier typescript
  2. npm ci
  3. npm ci
  4. observe that tsc and prettier are not present in the node_modules\.bin
  5. shake fist in confusion as previous scripts that pointed to tsc and prettier in the .bin folder fail

Environment

  • npm: 8.1
  • Node: 16.13.0
  • OS: Windows 10
  • platform: Surface Laptop
  • npm config:
; "builtin" config from C:\Program Files\nodejs\node_modules\npm\npmrc

prefix = "C:\\Users\\<REDACTED>\\AppData\\Roaming\\npm"

; "user" config from C:\Users\<REDACTED>\.npmrc

email = "not-used@example.com"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = <REDACTED>
; HOME = <REDACTED>
; Run `npm config ls -l` to show all defaults.

note: should be an option to remove customer information in the npm config ls

@wandyezj wandyezj added Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release labels Nov 10, 2021
@ruyadorno
Copy link
Contributor

Closing: this looks to be similar if not a duplicate of an existing issue, #4308. If you believe your instance is unique, please provide further clarifying details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release
Projects
None yet
Development

No branches or pull requests

2 participants