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.

Uncaught TypeError: Cannot read property 'commit' of null

See original GitHub issue

I upgraded from 0.0.11-1 to 0.0.12 and I’ve started seeing this error on a particular route of my app.

The full stack trace:

runtime.js:6407 Uncaught TypeError: Cannot read property 'commit' of null
    at Environment.commit (runtime.js:6407)
    at Environment.commit (environment.js:266)
    at InteractiveRenderer._renderRootsTransaction (renderer.js:359)
    at InteractiveRenderer._renderRoot (renderer.js:289)
    at InteractiveRenderer._appendDefinition (renderer.js:214)
    at InteractiveRenderer.appendOutletView (renderer.js:202)
    at invokeWithOnError (backburner.js:216)
    at Queue.flush (backburner.js:125)
    at DeferredActionQueues.flush (backburner.js:278)
    at Backburner.end (backburner.js:410)

Diff of dependencies:

-    "@fortawesome/ember-fontawesome": "0.0.11-1",
+    "@fortawesome/ember-fontawesome": "0.0.12",
     "@fortawesome/fontawesome-free-brands": "^5.1.0-3",
-    "@fortawesome/fontawesome-free-regular": "^5.1.0-3",
-    "@fortawesome/fontawesome-free-solid": "^5.1.0-3",
+    "@fortawesome/fontawesome-pro-light": "^5.0.8",
+    "@fortawesome/fontawesome-pro-regular": "^5.0.8",
+    "@fortawesome/fontawesome-pro-solid": "^5.0.8",

You can see I also upgraded to pro icons. Not sure if that has anything to do with it. It’s not out of the question that this error is unrelated to this library. But I thought it’s likely since it’s the only dependency that changed.

Issue Analytics

State:
Created 6 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

4reactions

mhluskacommented, Mar 7, 2018

@mlwilkerson I figured out the issue. It was completely unrelated to fontawesome. It was caused by a runtime error in a didInsertElement hook. Strange. Sorry for the distraction.

2reactions

tarponjargoncommented, Mar 20, 2018

@mhluska thanks for responding. I finally figured it out. I had two different components, both using ember-radio-button, that were using the same radioId.

Top Results From Across the Web

Cannot read property 'commit' of undefined VUEX

Please help me it always says Cannot read property 'commit' of undefined. Here is my code in store.js. import Vue from 'vue'; import...

Cannot read property 'commit' of undefined - Vue Forum

On my case, this error “Cannot read property 'commit' of undefined” was because of the order of the script (app.js):. First Vuex, after...

Vuex anybody? "TypeError: this.$store.commit is not a function"

Im getting an error here Error in created hook: "TypeError: Cannot read property 'commit' of undefined". Somebody might help me?

cannot read properties of undefined (reading '$store') - You.com

Here's an example of a JavaScript TypeError: Cannot read property of undefined thrown when a property is attempted to be read on an...

Cannot read property 'commit' of undefined in .vue and .js file ...

[Solved]-Vuex uncaught TypeError: Cannot read property 'commit' of undefined in .vue and .js file-Vue.js ... You are calling the mutation wrong. You are...