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

Splitting up Grunt watch into separate tasks to improve performance #287

Closed
theorise opened this issue Mar 10, 2016 · 1 comment
Closed

Comments

@theorise
Copy link

I am using Pattern Lab Node v1.3.0 on Mac, using the grunt configuration.

Expected Behavior

The grunt watch task rebuilds:

  • Patterns when updating .mustache files
  • CSS when updating .css files
  • JS when updating .js files
Actual Behavior

The grunt watch task rebuilds everything when running the watch task. This makes developing inside Pattern Lab a painful process once you have a large pattern repository.

Steps to Reproduce

Run grunt serve in a repository with a lot of patterns, update a style, see that you have to wait for the patterns to rebuilt despite having no changes.

@bmuenzenmeyer
Copy link
Member

closing as superseded by edition-node-grunt and lack of response on #289

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

No branches or pull requests

2 participants