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: nodesSelection.exit(...).transition is not a function

See original GitHub issue

We’re getting this error on v4.1.5:

graph-view.js:693 Uncaught TypeError: nodesSelection.exit(...).transition is not a function
    at RadiumEnhancer.GraphView._this.renderNodes (graph-view.js:693)
    at RadiumEnhancer.GraphView._this.renderView (graph-view.js:790)
    at RadiumEnhancer.render (graph-view.js:929)
    at RadiumEnhancer.render (enhancer.js:265)
    at finishClassComponent (react-dom.development.js:13085)
    at updateClassComponent (react-dom.development.js:13047)
    at beginWork (react-dom.development.js:13715)
    at performUnitOfWork (react-dom.development.js:15741)
    at workLoop (react-dom.development.js:15780)
    at HTMLUnknownElement.callCallback (react-dom.development.js:100)

This does not happen on this commit of the fork: https://github.com/vicapow/react-digraph/tree/d3-as-direct-dependency-dist

Issue Analytics

State:
Created 5 years ago
Comments:8 (7 by maintainers)

Top GitHub Comments

1reaction

estillercommented, Sep 22, 2018

Hey @ajbogh, I started writing a simple app using this component and I ran into the exact same issue that @NameFILIP mentioned above. I started investigating and found something very interesting - if I clone this (react-digraph) repository “as-is”, build it with yarn install and then try and run the example with yarn run example or npm run example - it reproduces the issue! However, what is weirder than that is that if I take this exact same repo and install dependencies with npm install then the same example works!

Moreover, if now I go to my own app (which has it’s dependencies installed with yarn install) and run npm install instead - then my app starts working… Can you think of any reason for this behavior? Which packages are resolved differently?

0reactions

ajboghcommented, Oct 8, 2018

@NameFILIP Thanks for testing out v4.1.6. I’ve fixed this issue with yarn by upgrading d3 to v5 in v4.1.7. For some reason yarn didn’t work correctly with v4.13.0. I’m hoping that upgrading to v5 doesn’t negatively impact anyone.

Top Results From Across the Web

d3 transition is not a function - Stack Overflow

I am having a problem with my D3 code. const hexagon = this.hexagonSVG.append('path') .attr( ...

Enter/Leave & List Transitions - Vue.js

Vue provides a transition wrapper component, allowing you to add entering/leaving transitions for any element or component in the following contexts:.

Uncaught TypeError | Is Not A Function | Solution - YouTube

Have you encountered an error like:- Uncaught TypeError - Some selector is not a function - jQuery is not a function - owlCarousel...

Transitions - Material UI - MUI

transition : A CSS transition value, which composes all CSS properties that should be transitioned, together with the defined duration, easing and delay....

Common Issues | Swup

Swup waits for any element with class transition-[something] to finish the ... In case the styles are missing and the element does not...