Another _Ember is undefined error
See original GitHub issueSymptoms
Same symptoms as #342, but the errors are coming up while loading tests in Travis. Every require
fails with this error.
How to replicate
You should be able to replicate by running tests with CI=true
.
It’s related to this default line in targets.js
. Removing ie 11
as a target removes the issue.
if (isCI || isProduction) {
browsers.push('ie 11');
}
Tested on latest ember-cli-babel@7.20.4
.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:20 (6 by maintainers)
Top Results From Across the Web
ember.js - Getting a model is undefined error after upgrading ...
Some other issue? Edit: Actually I think I have narrowed down what the error is. It doesn't seem to like the title being...
Read more >Cannot read property 'get' of undefined - Ember.JS
... but I have an error; routes/purchases.js: import Route from ... Lastly you're trying to get another property “pname” from something that ...
Read more >models is undefined · Issue #12845 · emberjs/ember.js - GitHub
I have another strange bug in ember. Sometimes i get an error when switching routes. TypeError: models is undefined. This error doesn't happen ......
Read more >The 8 Most Common Mistakes That Ember.js Developers Make
Ember.js is an awesome framework for building rich and powerful front-ends, ... The problem was that if the user then switched to another...
Read more >Uncaught type error: Cannot read property 'ajax' of undefined ...
Coding example for the question Uncaught type error: Cannot read property 'ajax' of undefined-ember.js.
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
Ya, sorry for this taking so long. It took a little while to figure out which specific babel plugins were mutating the nodes, and I only discovered that using the shared AST nodes was causing an issue due to stepping through the tranpsilation process.
#348 should land and be released as 7.20.5 soon.
OK, that sounds a lot like the scenario that @sandydoo called out and provided a reproduction for. I’ll be looking into it this afternoon.