-
Notifications
You must be signed in to change notification settings - Fork 323
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
Fixing the node.js dependencies, so the VSCode plugin can be built again #5738
Conversation
"vsce": "^2.6.4", | ||
"webpack": "^5.40.0", | ||
"webpack-cli": "^4.7.2" | ||
"@types/xml2js": "=0.4.11", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using ^
allows the node to download new version of the same library. That's often dangerous as new versions may not be fully compatible with previous ones. Using =
to fix to an exact version of each library. This configuration is known to work.
The VSIX extension is really built by our GitHub actions now. I guess this proves the node.js dependencies are now correct. @mwu-tow, if you agree, please merge. Thank you. |
Pull Request Description
Fixing node.js dependencies as:
was broken. Making sure the VSIX build is part of the actions workflow.
Important Notes
To reproduce/verify remove
enso/tools/enso4igv/node_modules
first and try to build.Checklist
Please include the following checklist in your PR:
style guides.