Trevor Johnson
Trevor Johnson
Similiar to this, if you upgrade to the latest version of sequelize, this package will not work when you perform a migration. You will get something like the error below...
Will this ever get merged?
Yes, I am using webpack. What we have been doing is excluding all node_modules from running through babel-loader. To work around this I had to identify the packages that were...
That issue seems similar. I downloaded the version that was linked for the fix [here](https://codesandbox.io/s/naughty-kalam-qg096) as part of #17666, but I am still seeing the memory leak.
The issue I have seems different than the one you have linked too. I am still working to more closely identify what is happening. I will post back here when...
The running version of react now in the sample app is 0.0.0-241c4467e, which is the same version from the app you linked to. This version has helped with the leak...
I have deployed the demo [here](https://tsjohns9.github.io/react-memory-leak/) for your convenience