-
Notifications
You must be signed in to change notification settings - Fork 1
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
Investigate install-issues with npm 5 #24
Comments
The issue seems to be with npm5, not minstall: npm/npm#17056. |
it seems, that npm sometimes automatically prunes packages. this could be a problem: npm/npm#16839 EDIT: EDIT2: |
This seems to currently be one of the most active npm-issues regarding this topic: npm/npm#16853 |
Can the cmd-option ˋ—no-auto-pruneˋ be a workaround? |
@moellenbeck The changes for that option contain only 10 lines of code, and @substack opened a PR on the main npm-repo 5 days ago (npm/npm#18921) but this PR is neither merged, nor its content published in the official npm yet |
After getting reports, that minstall 1.3.6 supposedly works with npm5, i can confirm that minstall 1.3.6 does definitely not work with npm5. IF it happened to have worked for you, then that is pure luck, but i have projects that do not work with npm5, even with minstall 1.3.6 I can however confirm, that minstall can be easily upgraded to work with npm5, should this PR get merged: npm/npm#18921 |
@heikomat I consider this as done. Do you agree? |
@heikomat As the issue states "Investigate (...)" I'm confident, we did this extensively. |
The installation with npm 5 seems to have a couple new issues that need to be addressed. Here are some error-logs:
The text was updated successfully, but these errors were encountered: