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

Compile only "changed files" from watch command #714

Closed
felixknox opened this issue May 18, 2016 · 3 comments
Closed

Compile only "changed files" from watch command #714

felixknox opened this issue May 18, 2016 · 3 comments

Comments

@felixknox
Copy link

felixknox commented May 18, 2016

Is it possible through the roots build scripts to set a setting that would allow for only changed files to get compiled?

Atm. with < 20 files it takes several seconds to compile any change.

This is primarily changes to ex. .styl, .coffee etc.

@jescalan
Copy link
Owner

Unfortunately it is not, because of dependencies - see #586 for a full explanation.

However, we are working on a next-generation version of roots called spike that holds on to a full dependency graph and solves this problem. It's in early stages so I wouldn't yet build any important production apps on top of it unless you want to be in close contact with us about bugs and breaking changes. Either way, in our experience so far it's been significantly faster in watch mode, so if you want feel free to keep an eye on it!

@felixknox
Copy link
Author

So Roots is getting "put on ice"?

@jescalan
Copy link
Owner

jescalan commented May 18, 2016

The plan at the moment is once spike is fully stable and released to put Roots on "LTS", basically in maintenance mode. No new features will be added, but bugs will be fixed, dependencies will stay up to date, and everything will continue working as is. Down the road we will decide how long of a period this will be, but it will be at least a year.

Essentially, we have done what we can with Roots, it works well for us and many others, and we use it at my company in production for a large number of sites. But in order to keep pushing forward we need to get past limitations that require significant restructures to resolve, and therefore are moving towards a different project in order to not push another roots release that will be so different that migrating to it from an existing roots project would be an obscene amount of work.

tl;dr Roots will stay entirely stable and well maintained into the future, but if you want bleeding edge features, we can make that happen with spike.

Edit: Also, roots will be moved to the static-dev organization sometime in the future. We are completely committed to keeping roots sites in good working order, and only will start winding it down once spike has completely outdone it on every feature.

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