-
Notifications
You must be signed in to change notification settings - Fork 61
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 decreasing npm run compile
times
#2875
Comments
I'm interested in taking a look into this this sprint if I have time (I'll prioritize other issues first) |
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
May 26, 2023
This PR uses esbuild instead of webpack to bundle the webviews. This dramatically reduces the time it takes to bundle the webviews, from >50 seconds to <1 second. This PR also modifies the npm scripts and VS Code launch configurations to always recompile the webviews before launching. I also set up eslint to be run before launching the extension. If the extension seems slower to launch in debug mode, this is why. Closes redhat-developer#2875 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
May 26, 2023
This PR uses esbuild instead of webpack to bundle the webviews. This dramatically reduces the time it takes to bundle the webviews, from >50 seconds to <1 second. This PR also modifies the npm scripts and VS Code launch configurations to always recompile the webviews before launching. I also set up eslint to be run before launching the extension. If the extension seems slower to launch in debug mode, this is why. Closes redhat-developer#2875 Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
May 29, 2023
This PR uses esbuild instead of webpack to bundle the webviews. This dramatically reduces the time it takes to bundle the webviews, from >50 seconds to <1 second. This PR also modifies the npm scripts and VS Code launch configurations to always recompile the webviews before launching. I also set up eslint to be run before launching the extension. If the extension seems slower to launch in debug mode, this is why. Closes redhat-developer#2875 Signed-off-by: David Thompson <davthomp@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, running
npm run compile
takes a while (> 1 minute on my computer). This long build time even more noticeable when running the tests, since the script to run the tests always re-compiles/bundles the extension before running the tests. It would be nice to investigate ways to reduce this compile time to make it easier to develop the extension.One option worth investigating is
esbuild
, which claims to be 100x faster than webpackThe text was updated successfully, but these errors were encountered: