Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`needs` not resolving after module change
See original GitHub issuehttps://github.com/emberjs/ember-qunit/compare/v2.1.0...v0.4.23
Prior to this^ change, the module variable would always be declared with a Constructor and now it begins as undefined and is assigned a value inside the setup function.
It seems this has broken the needs in my tests, which aren’t being properly resolved, I think as a result of the module not receiving the description either at all or not at the right time?
for now (if you’re running into this issue) you should be able to just shrinkwrap or pin the version of q-unit to 4.22, and things should go green again.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’ve reverted the changes introduced in
0.4.23and released0.4.24, which should fix any problems introduced by that release.Apologies to everyone affected, I’m looking into and will hopefully have a fix shortly