Can't install on MacOS
See original GitHub issueThanks for creating this!
While I realize that the package is meant to be used on a windows machine, I need to run npm install --save-optional win-node-env
on my MacOS machine to get it checked into our package.json
and package-lock.json
files.
Is there some other way I should go about doing that?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
How to Fix the "macOS Could Not Be Installed on Your ...
1. Restart Your Mac and Retry the Installation · 2. Set Your Mac to the Correct Date and Time · 3. Create Enough...
Read more >If an error occurred while updating or installing macOS
If an error occurred while updating or installing macOS · Check your internet connection · Install in safe mode · Install after repairing...
Read more >macOS could not be installed on your computer? Here's what ...
How to fix “macOS could not be installed on your computer” · 2. Try running the installer again while in Safe mode ·...
Read more >macOS Could Not Be Installed on Your Computer? Read This!
macOS Could Not Be Installed on Your Computer? Read This! · Fix 1: Restart the Mac and Reintall · Fix 2: Check your...
Read more >'macOS Could Not be Installed on Your Computer', Fix Now!
How to fix 'macOS could not be installed on your computer' · Fix 1: Restart your Mac and retry the installation · Fix...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bug reported: https://npm.community/t/npm-install-save-optional-fails-to-properly-modify-package-package-lock-json-if-it-fails/3446
That worked! Pretty strange that it doesn’t work doing
npm install --save-optional win-node-env
. I would even say that’s probably a bug in npm. Thanks for the help, and for the package!