We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<Redirect />
6.22.3
I created a reproduction repo: https://github.com/Lukas-Kullmann/react-router-memory-leak The steps to reproduce are described in that repo's readme.
Basically: Use <Redirect /> (or useRedirect()) in any of your components in your tests with jest + jsdom.
useRedirect()
I use node v20.11.1 and npm v10.4.0.
The test does not leak memory, no matter if you use <Redirect /> or not.
Some objects stay in memory after the test if you use a <Redirect />. Most notably: JSDOM's Window object(s).
Window
The text was updated successfully, but these errors were encountered:
Seem to be seeing a similar issue where tests are failing due a memory leak.
Has anyone deduced what is the latest version without this issue?
Sorry, something went wrong.
No branches or pull requests
What version of React Router are you using?
6.22.3
Steps to Reproduce
I created a reproduction repo: https://github.com/Lukas-Kullmann/react-router-memory-leak
The steps to reproduce are described in that repo's readme.
Basically: Use
<Redirect />
(oruseRedirect()
) in any of your components in your tests with jest + jsdom.I use node v20.11.1 and npm v10.4.0.
Expected Behavior
The test does not leak memory, no matter if you use
<Redirect />
or not.Actual Behavior
Some objects stay in memory after the test if you use a
<Redirect />
. Most notably: JSDOM'sWindow
object(s).The text was updated successfully, but these errors were encountered: