The problem occurs whenever a toast is open while using the react router to navigate to the tree viewer. If we can't find a fix, we might want to switch to a different notification library.
Staying on version 5.x resolves this issue, any version from 6.x to the current 9.1.3 have this issue. Since I'm not sure if this is an issue in our code, react-toastify, d3, or react-router, finding the issue seems difficult, so any help is appreciated.
The problem occurs whenever a toast is open while using the react router to navigate to the tree viewer. If we can't find a fix, we might want to switch to a different notification library.
Staying on version 5.x resolves this issue, any version from 6.x to the current 9.1.3 have this issue. Since I'm not sure if this is an issue in our code, react-toastify, d3, or react-router, finding the issue seems difficult, so any help is appreciated.