Crash browser tab while creating spy instance in React 16.0.0
See original GitHub issuerxjs-spy: 5.0.0 react: 16.0.0
I tried to include following lines in one of my redux ducks file.
import { spy } from 'rxjs-spy';
spy();
and it always crash the browser tab after long time loading.
Issue Analytics
- State:
- Created 6 years ago
- Comments:21 (12 by maintainers)
Top Results From Across the Web
React App failed to load and displayed "Aw Snap!" in chrome ...
At the top right, click More More and then New Incognito window. In the Incognito window, try opening the page. If it opens,...
Read more >react how to use useeffect Code Example - Code Grepper
useEffect is a hook for encapsulating code that has 'side effects,' and is like a combination of componentDidMount , componentDidUpdate , and ...
Read more >How to use Jest spyOn with React.js and Fetch - Meticulous
Follow this step-by-step guide on Jest's SpyOn method, with a practical example using React and Fetch. This post also includes a comparison ...
Read more >karma cannot read properties of undefined - You.com | The search ...
I am trying to test a method (refreshMemberList()) that contains a subscribe, but when I run the tests I get this error from...
Read more >jest-get-type | Yarn - Package Manager
... Fix a problem where creating folders ending with .js could cause a crash (#6818) ... jest 16.0.0 ... Clear the terminal window...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also, if you’ve not already tried it, you could try disabling the graphing and snapshotting plugins:
If that solves the problem, I’d still appreciate your including and error message and any steps to reproduce the problem with a new project.
FYI. As of version 6.1.0, the
sourceMaps
option should no longer use massive amounts of memory.