Error: unknown package: npm-container
See original GitHub issueI’ve stumbled upon an error trying to run on a Linux box an app that is running fine on OSX. I doubt it’s due to the architecture. It would probably fail on a different Mac as well.
The error is the following:
tanis@samantha:~/soulvenir-meteor$ meteor
Figuring out the best package versions to use. This may take a moment.
Refreshing package metadata. This may take a moment.
Could not resolve the specified constraints for this project:
Error: unknown package: npm-container
tanis@samantha:~/soulvenir-meteor$
Issue Analytics
- State:
- Created 9 years ago
- Comments:22 (2 by maintainers)
Top Results From Across the Web
Unknown Error on package installation - node.js
I am trying to install js-yaml package and getting such error, I am new in node and have no idea why it cause...
Read more >Common errors | npm Docs
Broken npm installation; Random errors; No compatible version found; Permissions errors ... Running a Vagrant box on Windows fails due to path length...
Read more >Troubleshooting Node.js Deploys - Heroku Dev Center
Then, compare the results with the package.json engines section. Make sure a Node version ... Error: Unknown error installing "10" of node.
Read more >Error Codes | Yarn - Package Manager
Packages omitting node-gyp usually do so in order to decrease the amount of packages in the final dependency tree when building the package...
Read more >Running under Docker - Node-RED
docker run - run this container, initially building locally if necessary ... extend the Node-RED image with the missing packages on running containers...
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 Free
Top 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
works for me:
This solution does not work when deploying with meteor up though, so it’s quite troublesome. I think the only solution to that is to actually keep the node modules committed.