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

roots watch never completes but roots compile works fine #59

Open
thirteenpixels opened this issue Jan 12, 2016 · 4 comments
Open

roots watch never completes but roots compile works fine #59

thirteenpixels opened this issue Jan 12, 2016 · 4 comments

Comments

@thirteenpixels
Copy link

If I run roots compile everything works well, files are generated correctly, in the right location, etc.

If I run roots watch however, the process hangs at the compiling... step and never finishes.

With roots-contentful out of the project watch works perfectly.

@zspecza
Copy link
Contributor

zspecza commented Jan 13, 2016

Hi @thirteenpixels, I'm having trouble reproducing this. Could you perhaps provide me with some more information?

Ideally:

  • Your Node version $ node --version
  • Your NPM version $ npm --version
  • Your roots-contentful version (find this in your projects' package.json)
  • Your Roots version $ roots --version

@thirteenpixels
Copy link
Author

Absolutely, sorry should've provided that from the jump.

$ node -v v4.2.1 $ npm -v 2.14.7 $ roots -v 3.1.0 "roots-contentful": "0.0.9",

As an aside, and I can open another issue for this, it appears that while it says it's done compiling when I run it manually I've noticed it doesn't process my .sass files either. Removing roots-contentful from the project makes those render fine as well.

@zspecza
Copy link
Contributor

zspecza commented Jan 18, 2016

@thirteenpixels I've looked deeper into this and still have trouble reproducing it unless there are multiple top-level Sass files (I'm not a Sass user though). Would you be able to confirm if this is the same issue you are experiencing or a different one? What happens if you update to Node 5 and NPM 3, out of interest? (There is an issue for the sass bug on Accord's repo: jescalan/accord#137)

@thirteenpixels
Copy link
Author

I wasn't aware of that bug, thanks @declandewet . We'll do some testing and see if that's the culprit.

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