0.9.0 does not work
See original GitHub issueI tried to install 0.9.0 in an addon, and got the error that it couldn’t import ember-compatibility-helpers
. Manually installing that addon didn’t help either. Downgrading to 0.8.27 made it work.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:9 (3 by maintainers)
Top Results From Across the Web
WinCompose 0.9.0 does not start on my machine #263 - GitHub
I downgraded to 0.8.2 and it works with no issues. I run Windows 10 Pro. ... WinCompose 0.9.0 does not start on my...
Read more >I have just started coding and when I type Pragma solidity ...
I have just started coding and when I type Pragma solidity >=0.6.0 <0.9.0; it gives me error. I couldn't know how to do...
Read more >FreeMind - Browse /freemind/0.9.0 at SourceForge.net
A premier mind-mapping software written in Java.
Read more >Troubleshooting — librosa 0.9.0 documentation
For bug reports and other, more technical issues, consult the github issues. Here are a few of the most common problems that users...
Read more >0.9.0 Release Notes The Zig Programming Language
One can link with libc or other libraries to fill in the gaps in the standard library. These targets are known to work,...
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
In an addon, it ended up being what was described here: https://github.com/pzuraq/ember-compatibility-helpers/issues/32
TLDR, the addon had this in the index.js included hook:
Which should actually be:
Pretty counter intuitive that this would lead to this error… But changing this made the addon run for me again (with 1.0.0).
Seeing this too… looks like there was a minor version bump somewhere? I didn’t change any dependencies, but yarn.lock shows some upgrades. Anyone know what’s happening?