-
Notifications
You must be signed in to change notification settings - Fork 397
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
Allow separate setup and build frontend tasks #221
Comments
++ |
Would also be good to document caching the npm and bower assets in .travis.yml |
@gapple @sarahjean If I run |
@grasmash That'd be nice but it doesn't seem to behave that way. I think composer is a little better behaved in that regard. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
More expensive operations like
npm install && bower install
only need to be run on initial setup and when dependencies change.Separating them into a
frontend:setup
task would allowfrontend:build
to run fewer operations and take less time during development.The text was updated successfully, but these errors were encountered: