`ember fastboot` does not terminate with ember-cli >= 2.13
See original GitHub issueReproduction:
ember new app
cd app
ember install ember-cli-fastboot
ember fastboot
// press ctrl-c
This shows cleaning up...
but the process never terminates. Just sending a SIGKILL
will terminate it. No problems like that with ember serve
, or when downgrading to ember-cli 2.12.
Don’t know if it’s worth fixing, as ember fastboot
is deprecated anyways, but it broke some test setups, see https://github.com/tomdale/ember-cli-addon-tests/issues/96
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
_emberMetalProperty_get.get(...).getURL is not a function ...
At the end fastboot/lib/result.js calls the _finalize method and then _finalizeMetadata . _finalizeMetadata calls instance.getURL() and then for ...
Read more >Shoebox - Ember FastBoot
FastBoot is an addon you can add to existing Ember CLI apps. ... To stop the server, press Ctrl-C on your keyboard to...
Read more >ember-fetch - npm
ember -fetch uses node-fetch in Fastboot, which doesn't allow relative URL. url should be an absolute url, such as https://example.com ...
Read more >Part 2: Should you use Ember FastBoot or not? - DockYard
In this part we'll look at the performance considerations for FastBoot and the ROI for your use-case.
Read more >ember-fetch | Yarn - Package Manager
ember -fetch requries ember-cli 2.13 or above. Usage ... To use ember-fetch with TypeScript or enable editor's type support, You can add "fetch":...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I wanted to kill things in a subsquent PR since that PR has got really long to review for anyone.
The deprecation message already exists today. See here . I am totally fine with leaving it for few more releases too.