Require cycle: node_modules/core-js/internals/microtask.js warning
See original GitHub issueDescription
Getting this error when I build my React Native app
ERROR RangeError: Maximum call stack size exceeded, js engine: hermes
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes
WARN Require cycle: node_modules\core-js\internals\microtask.js -> node_modules\core-js\internals\microtask.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes
React Native version:
info Fetching system and libraries information...
System:
OS: Windows 10 10.0.19043
CPU: (4) x64 Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz
Memory: 2.12 GB / 15.89 GB
Binaries:
Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.18.1 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version 4.1.0.0 AI-201.8743.12.41.7199119
Visual Studio: Not Found
Languages:
Java: 11.0.10
npmPackages:
@react-native-community/cli: Not Found
react: ^17.0.2 => 17.0.2
react-native: ^0.64.2 => 0.64.2
react-native-windows: Not Found
npmGlobalPackages:
*react-native*: Not Found
Steps To Reproduce
I’m not sure what caused it but it is similar to this commenter and issue #31173. The solution provided in #31173 is to disable Hermes but I would like to leave Hermes enabled since it is supposed to provide performance improvements.
Expected Results
No error in Metro
Snack, code example, screenshot, or link to a repository:
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7
Top Results From Across the Web
Require cycles are allowed, but can result in uninitialized values
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. - node_modules\react- ...
Read more >Realm node package has "cycle" warnings - MongoDB
js Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
Read more >Node.js v19.3.0 Documentation
Warning : binding inspector to a public IP:port combination is insecure ... Core modules; Cycles; File modules; Folders as modules; Loading from node_modules ......
Read more >Require Cycle Warnings : r/reactnative - Reddit
Howdy peeps. I like using the index.js to export a bunch of components I designed and it keeps giving me Require Cycle Warning...
Read more >this can also happen when the js bundle is corrupt or there is ...
Version. Node - v16.13.1 React - 17.0.2 React -Native 0.66.4 ... js engine: hermes WARN Require cycle: node_modules\core-js\internals\microtask.js ...
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
Any updates on this? When I set
inlineRequires = false
, the app builds successfully but I’d like to keep inline require enabled if possible@safaiyeh Sorry it’s taken me so long to get back to you! So I figured out the part that’s causing the error but I’m unsure how to resolve it as it was working prior. It’s being caused by the
AppRegistry.registerComponent(appName, () => Root);
when I change theRoot
toApp
, it works fine but I would like to have the dev meu toggle visible still. Also, another weird thing to note is that my code as-is works well in iOS with only the require cycle error (as opposed to on android where i also get anInvariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
error) I had followed the instructions from this blog: https://spicyseashells.com/article/react-native-storybook to implement the dev menu toggle for storybook.My code (excluding import statements for brevity):