-
Notifications
You must be signed in to change notification settings - Fork 159
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
npm run test:precook
broken
#194
Comments
I was unable to repro this on Node v5.0.0/npm v3.3.6. What node/npm/OS are you on? |
Node 4.2.0 on OSX/El Capitain. I think we're going to have to support Node 4 since it's LTS. It doesn't make it impossible for me to develop. Just makes it slower. I can understand if we prioritize other things. |
I think this should work on Node 4. Has anyone else run into this? @arjansingh, is there anything unusual going on with symlinking or something? Something weird in your Brocfile? |
@arjansingh Is this related to the |
@danmcclain No. The I did have FWIW, I ran it with [email protected] locally with no dependencies sym linked and now get this error:
[email protected] works @habdelra. I can also confirm that. |
still an issue on node 4. although i think we should re-work how we do tests to mitigate the need at all. |
Agreed. #396 is tracking on re-working the tests as well. |
…te_body_in_domContents Moved the script tag fastboot-body-start boundary in _finalizeHTML method
Tried precooking to save my self some time. It looks like it's doing some weird recursion. Anyone got a clue what's going on here?
The text was updated successfully, but these errors were encountered: