Quantcast
Channel: Ember.JS - Latest topics
Viewing all articles
Browse latest Browse all 4826

Ember 3.6: any new reasons one might see "Uncaught Error: unreachable"

$
0
0

@Hummingbird wrote:

Has there been any other recent cause for the following error other than reusing html elements inside handlebars expressions?

I am dynamically calling the same component via {{component ‘coponent-name’}} at two places. One works and one just triggers the error. Tried to use templatelint rule no-shadowed-elements, but it did not show anything.

Uncaught Error: unreachable
    at unreachable (util.js:13)
    at Object.APPEND_OPCODES.add [as evaluate] (runtime.js:845)
    at AppendOpcodes.evaluate (runtime.js:39)
    at LowLevelVM.evaluateSyscall (runtime.js:2179)
    at LowLevelVM.evaluateInner (runtime.js:2153)
    at LowLevelVM.evaluateOuter (runtime.js:2146)
    at VM.next (runtime.js:3643)
    at VM.execute (runtime.js:3633)
    at TryOpcode.handleException (runtime.js:2798)
    at UpdatingVMFrame.handleException (runtime.js:2921)

I tried to downgrade back to ember 3.5 and everything works without issues again. Upgrade to 3.6 and the error reappears.

Any suggestions on how to get down to the cause of this? Any hints on debugging what might cause runtime.js to fail?

Posts: 1

Participants: 1

Read full topic


Viewing all articles
Browse latest Browse all 4826

Trending Articles