npm / npm/cli

[BUG] <npm install cause Mac restart>

Open
#4,801 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage Release 8.x
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

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

During the process of npm install --save-dev @nomiclabs/hardhat-waffle ethereum-waffle chai @nomiclabs/hardhat-ethers ethers my Mac screen suddenly turned black and restart. I tried this command many times and this situation arised every time.

My Mac is MacBook Pro(Chip Apple M1 Max). And my fellow colleagues's MacBook Pro(Chip Apple M1 Pro) works wells with the same command.

When I npm install other packages it turns out well.

Expected Behavior

Install package without error.

Steps To Reproduce
  1. Item2 + zsh
  2. cd /Users/treaser/Programming/TeaLib/eth-app/contracts
  3. Run 'npm install --save-dev @nomiclabs/hardhat-waffle ethereum-waffle chai @nomiclabs/hardhat-ethers ethers'
  4. My Mac Crush
Environment
  • npm: 8.7.0
  • Node.js: v16.13.1
  • OS Name: macOS Monterey 12.0.1
  • System Model Name: MacBook Pro (14-inch, 2021) Chip Apple M1 Max
  • npm config:
; copy and paste output from `npm config ls` here
; "user" config from /Users/treaser/.npmrc

http-proxy = "https://127.0.0.1:41080"
https-proxy = "socks5h://127.0.0.1:1080"
proxy = "socks5h://127.0.0.1:1080"
registry = "https://registry.npm.taobao.org/"

; node bin location = /Users/treaser/.nvm/versions/node/v16.13.1/bin/node
; node version = v16.13.1
; npm local prefix = /Users/treaser/Programming/TeaLib/eth-app/contracts
; npm version = 8.7.0
; cwd = /Users/treaser/Programming/TeaLib/eth-app/contracts
; HOME = /Users/treaser
; Run `npm config ls -l` to show all defaults.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no repository file or test. Start by reproducing the exact npm install command with the listed Node.js, npm, macOS, proxy, and registry settings, then compare it with the reported working package installs. Done means identifying a reproducible npm cause for the restart or establishing that the failure is outside npm.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, macos, nodejs
Domain
cli, operating-systems, tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.