-
Notifications
You must be signed in to change notification settings - Fork 250
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
review-issue-1228: speed up javascript task #1229
Conversation
👍 .. will test tomorrow and comment |
Can we add a watch which will check if any JS is updated if not do not rebuild or copy these JS files? |
@aniketdharia this is just a fix for the javascript compilation, we still have a watch at the end of the dev task. |
@aniketdharia i can only do that by removing the clean task on build, otherwise you've nothing to compare the srcfiles to because the clean task deletes the contents of the build folder |
to explain a bit, this pr is three ideas in one and is not intended to be merged, they are:
they'll have to be separate prs if we agree these things are a boon to productivity |
+1 from me.. personally as it is improving the speed even of grunt dev if we make similar changes... the option of avoiding unnecessary javascript and less compilation reduces the build time drastically... as once the theme and components are fixed for a curriculum, the only updates that would happen are in JSON files. Basically publishing tasks. |
need to split into separate prs |
#1228
javascript:dev takes 2.2seconds - down from 3
javascript:compile takes 5 seconds - down from 14