-
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
Have one way to build static/karma.js #3599
Comments
I agree with And sorry that you had to learn it the hard way, I probably should have made the complete switch in a single commit instead of doing only part of the work. PS The correct way to build the client it is outlined in the docs:
|
If you use the |
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
🎉 This issue has been resolved 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
I just discovered the hard way that
static/karma.js
can be created withgrunt browserify
ornpm scripts/client.js build
It seems like
grunt watch
relies on the first and travis relies on the second.I propose to remove
grunt browserify
@devoto13 WDYT?
The text was updated successfully, but these errors were encountered: