-
Notifications
You must be signed in to change notification settings - Fork 24
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
Feature: Update babel-loader
webpack config to have caching support for faster builds
#452
Conversation
@gagan0123 Good find, however, I wouldn't want to try this near a release. Let's try it in the Related comments: babel/babel-loader#199 (comment), babel/babel-loader#351 (comment) |
439ca70
to
184d81a
Compare
Created new branch, cherry-picked my commit, then force pushed to this, so as to isolate it from other changes that were being displayed, now its ready for review and merge to |
cc @mohdsayed |
Anything else that needs to be added in this PR? |
That's all for post v0.5 merge |
📝 Noted We can assign this to QA after 0.5 release 🚀 |
QA DONE: LGTM I have tested all the scripts:
And run the extension and test a few audits |
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.
Merging this long pending PR.
cc: @mayan-000 , @amovar18 , @ayushnirwal
Description
This PR aims to improve the build performance of our Webpack configuration by implementing caching for the Babel loader. By enabling this feature, we expect to see a significant reduction in build times, particularly during development, as Babel will be able to reuse previously computed results instead of reprocessing files from scratch on every build.
Relevant Technical Choices
Testing Instructions
To verify the effectiveness of this change:
Additional Information:
This change is a straightforward enhancement aimed at improving developer experience by reducing waiting times during the build process when switching between branches. It does not introduce any new dependencies or major changes to our build configuration.
Checklist