Skip to content
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

improve grunt watch task #788

Closed
leobalter opened this issue Mar 18, 2015 · 2 comments
Closed

improve grunt watch task #788

leobalter opened this issue Mar 18, 2015 · 2 comments

Comments

@leobalter
Copy link
Member

In a private chat I saw @jzaefferer's will to improve speed on our grunt watch task.

Current options to try (not exclusive):

Some goals:

  • grunt watch needs to be faster
  • don't rebuild src files when only test files are modified
  • can we use those tools to run jshint/jscs only at the modified files (src or each test files)
  • run tests in parallel (if this goes faster)
@rdugue
Copy link
Contributor

rdugue commented Oct 23, 2015

I made some changes on a branch to run jshint/jscs only modified files but it is actually making grunt watch run ~2 seconds slower for me. You can see the change I made here. I'm going to test some more.

--edit: grunt watch seems to run significantly faster with spawn set false and interrupt set true.
--edit 2: Running tasks with grunt-concurrent seems to also improve speed.

rdugue added a commit to rdugue/qunit that referenced this issue Oct 24, 2015
rdugue added a commit to rdugue/qunit that referenced this issue Oct 24, 2015
rdugue added a commit to rdugue/qunit that referenced this issue Oct 25, 2015
rdugue added a commit to rdugue/qunit that referenced this issue Oct 26, 2015
Changed the grouping of the concurrent tasks

Ref qunitjs#788
leobalter pushed a commit that referenced this issue Oct 27, 2015
@leobalter
Copy link
Member Author

Closed by #886

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants