Hot Reloading `Maximum call stack size exceeded` error with circular reference
See original GitHub issueSay, there are two files a.js
and b.js
.
a.js
:
require('./b');
b.js
:
require('./a')
After change one of this file, with Hot Reloading enabled, it will run into an infinite situation and cause Maximum call stack size exceeded
finally.
Even if I use a dynamic require in a function, such as what in b.js
:
function f(){
require('./a')
}
Issue Analytics
- State:
- Created 7 years ago
- Reactions:19
- Comments:24 (7 by maintainers)
Top Results From Across the Web
Understanding "RangeError: maximum call stack size exceeded"
A circular reference will create errors because it will not evaluate to a declared value (number, string, boolean), nor to 'undefined'.
Read more >JavaScript Errors and How to Fix Them - David Walsh Blog
How to fix this error: Remove circular references like in the example from any ... Uncaught RangeError: Maximum call stack size exceeded.
Read more >T163523 Vagrant provision fails for restbase (Maximum call ...
Scheduling refresh of Service[restbase] ==> Exec[/vagrant/srv/restbase_npm_install]/returns: npm ERR! Maximum call stack size exceeded .
Read more >Changelog - Cypress Documentation
Fixed a regression in 6.5.0 that could cause Cypress to crash with a RangeError: Maximum call stack size exceeded at _deconstructPacket error.
Read more >Modify circle but don't allow to change center in OpenLayers
Error loading geoJSON into map using OpenLayers v4.2.0 ... Trying to change point style -> RangeError: Maximum call stack size exceeded.
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 Free
Top 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
This issue is still happening as of 0.48.0. This should be opened again
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.