-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
chore(build): unify client bundling scripts #3600
Conversation
Remove bundling logic from Grunt and introduce watch mode into the scripts/client.js. New script (`npm run build:watch`) allows to watch for the changes in client sources and bundle them automatically. This also fixes a bug where `npm run build` could swallow errors and silently do nothing. Fixes karma-runner#3599
✅ Build karma 416 completed (commit 10de10529f by @devoto13) |
✅ Build karma 415 completed (commit 10de10529f by @devoto13) |
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.
Thanks!
Hmm. I just realized that every time I change branches I may need an |
@johnjbarton No, normally you don't need to run it after changing branches. Since we commit bundled client code to the repository, you only need to run |
but if the new branch has a change to /client/karma.js the committed static/karma.js will be out of sync with the branch right? |
Well, if one didn't run |
oh yes thanks! |
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Remove bundling logic from Grunt and introduce watch mode into the scripts/client.js. New script (`npm run build:watch`) allows to watch for the changes in client sources and bundle them automatically. This also fixes a bug where `npm run build` could swallow errors and silently do nothing. Fixes karma-runner#3599
Remove bundling logic from Grunt and introduce watch mode into the scripts/client.js. New script (
npm run build:watch
) allows to watch for the changes in client sources and bundle them automatically.This also fixes a bug where
npm run build
could swallow errors and silently do nothing.Fixes #3599