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
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
I've been running into problems where an optionalDependencies entry is specified but npm treats it exactly like a regular dependency, which causes the whole install to fail instead of ignoring the optional package. This feature seems really weird. npm should just ignore optionalDependencies outright and if people want extra magic they can fiddle with the packages themselves.
The text was updated successfully, but these errors were encountered:
The "try-and-continue-on-failure" behavior seems to be not surprising to most people. I think you had an old version that only continued on certain types of failures, but not others, which was the problem you ran into.
I've been running into problems where an optionalDependencies entry is specified but npm treats it exactly like a regular dependency, which causes the whole install to fail instead of ignoring the optional package. This feature seems really weird. npm should just ignore optionalDependencies outright and if people want extra magic they can fiddle with the packages themselves.
The text was updated successfully, but these errors were encountered: