question-mark
Stuck on an issue?

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.

[Bug] Cannot read properties of undefined (reading 'shouldSupersede')

See original GitHub issue

🐞 Describe the Bug

When calling routerService.urlFor(...) the call throws the following error:

TypeError: Cannot read properties of undefined (reading 'shouldSupersede')
    at NamedTransitionIntent.applyToHandlers (http://localhost:4040/assets/vendor.js:58167:52)
    at NamedTransitionIntent.applyToState (http://localhost:4040/assets/vendor.js:58109:19)
    at PrivateRouter.generate (http://localhost:4040/assets/vendor.js:59134:26)
    at Router.generate (http://localhost:4040/assets/vendor.js:18718:38)
    at RouterService.urlFor (http://localhost:4040/assets/vendor.js:15630:27)
    at CatchAllRoute.urlForRouteInfo (webpack://cargo/./node_modules/ember-error-route/index.js?:84:24)
    at CatchAllRoute.serialize (webpack://cargo/./node_modules/ember-error-route/index.js?:60:21)

🔬 Minimal Reproduction

😕 Actual Behavior

The error page does not work properly.

🤔 Expected Behavior

The call does not fail and the error route is displayed correctly.

🌍 Environment

  • Ember: 4.3.0 (works fine in 4.2.0)
  • Node.js/npm: irrelevant
  • OS: irrelevant
  • Browser: irrelevant

➕ Additional Context

This is most likely related to the changes that were introduced in https://github.com/emberjs/ember.js/pull/19971

/cc @wagenet

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:12 (11 by maintainers)

github_iconTop GitHub Comments

3reactions
Turbo87commented, Oct 12, 2022

I can confirm that CI is green now. thanks again!

3reactions
chriskrychocommented, Oct 12, 2022

@Turbo87 if you can confirm once Renovate bumps that PR to use 4.7.1, I think we can close this out, as I published 4.4.3 LTS and 4.7.1 stable an hour ago! 🚀

Read more comments on GitHub >

github_iconTop Results From Across the Web

Ember Cannot read property 'shouldSupercede' of undefined ...
One reason for this issue is a {{#link-to}} pointing at a route that has a dynamic segment without providing that segment.
Read more >
Cannot read property 'shouldSupercede' of undefined - John ...
Ran into a problem of "Uncaught TypeError: Cannot read property 'shouldSupercede' of undefined" Turns out the issue was that my route had a ......
Read more >
Ember Cannot read property 'shouldSupercede' of undefined ...
Coding example for the question Ember Cannot read property 'shouldSupercede' of undefined with a new route-ember.js.
Read more >
typeerror: cannot read properties of undefined (reading 'route')
Describe the bug I have used preact-cli to create a new TypeScript project and have made zero changes to the code. I then...
Read more >
Timeline Bug - "cannot read properties of undefined ... - Reddit
Timeline Bug - "cannot read properties of undefined (reading 'minutes')". Hello! Earlier I had edited a few things in the Campfire Mobile ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found