Closed jakespeare closed 3 years ago
Oops!
I think somehow there were two separate Cytoscape libraries in my app. I'm not sure how that happened 🤔 , as I thought I was being diligent with my libraries. I discovered this when I was debugging one side of cytoscape with console statements and there were no console statements where the error occurred, but there were console statements where the extension registration occurred. Even after investigating dependencies for a while, I didn't see anything wrong with my package.json. I reinstalled these a few times. Ultimately it was just a sneaky sneaky bug locally, so not a problem with cytoscape/dagre.
If anyone else gets this, with all of the above yarn add
ed, try another yarn remove cytoscape
yarn add cytoscape
.
Thanks a lot! That was my problem too. I was tracking it down for hours already. <3
I'm not sure if it's all extensions or just Dagre, but "cytoscape.use(dagre)" seems to not be working. This is combined with the react-cytoscape library. Below is a censored sample of the code
What's especially weird is that I had this same bug in another app, and while trying to fix it, it seemingly magically disappeared. It comes back sometimes in the other app, and I don't know how it gets fixed. So for this new app, I made sure to follow the docs again to a T, but the evil bug reappeared. It works fine without using dagre as a layout. Let me know if I can provide some more information. My dependency versions:
I made sure that cytoscape.use() is being called before this too. Thanks in advance