You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nemo@ip-192-168-20-209 ~/r/quotabook-frontend (feat/security-sign-fixes) [SIGABRT]> npm install -g pnpm
(node:17357) ExperimentalWarning: CommonJS module /opt/homebrew/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /opt/homebrew/lib/node_modules/npm/node_modules/supports-color/index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
⠙dyld[17357]: missing symbol called
fish: Job 1, 'npm install -g pnpm' terminated by signal SIGABRT (Abort)
Environment
npm: 10.9.0
Node.js: v23.3.0
OS Name: macOS Sequoia 15.1.1 arm64
System Model Name: MacBook Pro
npm config:
; "builtin" config from /opt/homebrew/lib/node_modules/npm/npmrcprefix = "/opt/homebrew"; node bin location = /opt/homebrew/Cellar/node/23.3.0/bin/node; node version = v23.3.0; npm local prefix = /Users/nemo/repo/quotabook-frontend; npm version = 10.9.0; cwd = /Users/nemo/repo/quotabook-frontend; HOME = /Users/nemo; Run `npm config ls -l` to show all defaults.
The text was updated successfully, but these errors were encountered:
@scarf005 I tried it on my mac and i was able to install pnpm without an issue
kchindam-infy@kalyankumars-MacBook-Pro test % uname -m
arm64
kchindam-infy@kalyankumars-MacBook-Pro test % node -v
v23.3.0
kchindam-infy@kalyankumars-MacBook-Pro test % npm -v
10.9.1
kchindam-infy@kalyankumars-MacBook-Pro test % npm install -g pnpm
(node:75398) ExperimentalWarning: CommonJS module /Users/kchindam-infy/.nvm/versions/node/v23.3.0/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /Users/kchindam-infy/.nvm/versions/node/v23.3.0/lib/node_modules/npm/node_modules/supports-color/index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
added 1 package in 979ms
1 package is looking for funding
run npm fund for details
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
i'm unable to install any packages.
Expected Behavior
npm works.
Steps To Reproduce
npm install -g pnpm
Environment
The text was updated successfully, but these errors were encountered: