-
Notifications
You must be signed in to change notification settings - Fork 25
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
vscode-ext: move to esbuild bundling, cleanup #1232
vscode-ext: move to esbuild bundling, cleanup #1232
Conversation
@cab404 is attempting to deploy a commit to the Quantified Uncertainty Team on Vercel. A member of the Team first needs to authorize it. |
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.
Impressive wins!
a13cd44
to
bb6c680
Compare
This removes node_modules from dependencies all together fixing long time issue with yarn putting only a subset of dependencies in the extension source tree. It as well makes extension footprint 15x smaller. (down to 2.3Mb) Kinda fixes quantified-uncertainty#1162? It actually un-patches vsce though — it really is not an issue it should be solving :D
bb6c680
to
13a54f3
Compare
7d78024
to
28e944d
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Website build error is not important (it's because you forked before I did Vercel migration), but lint error should be fixed.
Other than that, looks good now.
This removes node_modules from dependencies all together,fixing long time issue with yarn putting only a subset of dependencies in the extension source tree.
It as well makes extension footprint 15x smaller. (down to 2.3Mb)
Kinda fixes #1162? It actually un-patches vsce though — it really is not an issue it should be solving :D