-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
About optionalDependencies
on package.json
#3486
Comments
Them are there just because:
|
I suppose it will be useful for CI, for the rest of the cases I don't quite see the usefulness because those dependencies for production do not seem to be necessary and for development they seem highly recommended (although not required). I do not know why:
Installs the same 1172 dependencies and doesn't skip the optional ones. |
Could be an issue with your npm version? What is your npm/nodejs version? |
I was previously using nodejs 18, this last weekend I upgraded it to nodejs 20 and retry to install zwave-js-ui with same result.
|
I may be missing something here but optional dependencies should be skipped, I will look at this tomorrow, thanks for letting me know 🙏🏻 |
Great, now it install 445 packages vs previous 1172 packages. |
@alexojegu thanks for your feedback Alex glad the issue is now solved 🙌🏻 |
It is really necessary to have packages like
eslint
,mocha
,c8
, etc. asoptionalDependencies
. If I'm not ignoring something, it seems that it would be more correct for them to bedevDependencies
.I say this because when installing
zwave-js-ui
as an NPM package it installs 1172 packages and among them I can see for example:The text was updated successfully, but these errors were encountered: