-
Notifications
You must be signed in to change notification settings - Fork 59
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
Using timezone in environment.js crashes fastboot #55
Comments
Thanks for the example app, I'll need a few days to dig into it. /cc @rlivsey who had done some work to implement fastboot support who may have encountered this |
Update: The first time I try and build ember-cli-fastboot fails with:
This looks to be happening when fastboot tries to npm install. Since it's failing there for me, it's likely why I'm not seeing the error you are pointing out. This error looks unrelated to ember-moment/ember-cli-moment-shim but I'll need to figure out how to resolve that before tackling this issue. |
Update 2: looks like the above issue is a race condition between fastboot and when the dist folder is created. I was not able to see your issue after that. Can you try backing down to |
Trying it now |
It looks like this might be unrelated to The first time I run it, it runs correctly. The second time, (just ^C between), it crashes with:
|
Yeah, I believe this to be a symptom of the same race condition I pointed out above. There are string of issues that seem to be stemming around the same thing, the Can you open a new issue against ember-cli-fastboot? I'll dig deeper tomorrow. |
Ok, I did now Thanks for quick feedback. I'll open a new issue and reference this for reference. |
Apologies if it's against wrong repo. I'm not yet sure how to distinguish between fastboot and addon errors.
Steps to reproduce:
to
environment.js
:NODE_DEBUG=fs ember fastboot --serve-assets
This error persists even if I remove the above lines in the
environment.js
Repo with the above problem: https://github.com/gandalfar/moment-fastboot-example
The text was updated successfully, but these errors were encountered: