Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Hot reload and "You try to add new component with already existing name" error
See original GitHub issueDescribe the bug
In dev mode, during application reload, require with name reports the above error.
To Reproduce Steps to reproduce the behavior:
- add
requirewithname - in developer mode, call hot reload of the app
This error cause that we are unable to work in dev mode. Will deleting line of code with this throw have any negative consequences (e.g. memleak in developer mode)?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Hot reload for components is a mess with the "HOTRELOAD ...
Basically, whenever you hot reload changes to a component, the component name gets mangled into something like “HOTRELOADED_<YourComponentName> ...
Read more >react-hot-loader/Troubleshooting.md at master - GitHub
I can access my Single Page App (SPA) only via / on refresh React-hot-loader: a Unknown was found where a Unknown was expected....
Read more >process is not defined on hot reload - Stack Overflow
I have a react app made with create react ...
Read more >Troubleshooting XAML Hot Reload - Visual Studio (Windows)
Error indicates that the change you're attempting isn't supported by XAML Hot Reload. Stop the debugging session, make the change, and then ...
Read more >Hot Reloading in React - Medium
React Transform is an experimental project I started… ... of the new component types, and somehow “attach” them to the existing DOM and ......
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
Closed in https://github.com/kirillzyusko/react-native-bundle-splitter/commit/b0e3ee6a1396e18f84e64e4597459132fb0c8968
Thanks for the clarification 😃 Your coding-style is better. But in the app we’re working in, it would require a large code refactor. Therefore, console.warn will actually be a better idea.