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

Allow separate setup and build frontend tasks #221

Closed
gapple opened this issue Jul 13, 2016 · 4 comments
Closed

Allow separate setup and build frontend tasks #221

gapple opened this issue Jul 13, 2016 · 4 comments
Assignees

Comments

@gapple
Copy link
Contributor

gapple commented Jul 13, 2016

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 allow frontend:build to run fewer operations and take less time during development.

@sarahjean
Copy link

++

@sarahjean
Copy link

Would also be good to document caching the npm and bower assets in .travis.yml

@grasmash
Copy link
Contributor

@gapple @sarahjean If I run npm install or bower install against a directory that already has built dependencies, won't it just skip installing them?

@sarahjean
Copy link

@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.

grasmash added a commit to grasmash/bolt that referenced this issue Aug 15, 2016
@grasmash grasmash self-assigned this Aug 15, 2016
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

3 participants