Releases: geowarin/electron-hot-loader
v0.8.0
Improve error handling
Previously, when a compiled JSX contained logical errors, or referenced a script containing an error, this error was swallowed.
This is no longer the case.
Because of a bug in chrome, electron-hot-loader
uses console.error
to display the error stack and make extra sure that you will see exactly where the error happened.
See PR #9.
v0.7.0
v0.6.1
v0.6.0
Do not instrument components in node_modules
Those components won't be edited by the users so it is wasteful to instrument them.
See #6
Apply semistandard
I feel electron-hot-loader
gets closer to a 1.0.0 release.
No one should be arguing about syntax in a PR.
v0.5.0
v0.4.0
Improve error handling
Error messages are now simplified when they happen in nested requires.
Do not instrument when the require call is not resolved
electron-hot-loader parses the require statements at the top of your file to resolve each component file.
Sometimes, it is not possible to make the connection between a React.createElement
and its require import.
This happens a lot with frameworks (like react-router or redux) that provide components that are not available in the default import.
electron-hot-loader will just ignore those components from now on, which should prevent errors from happening.
If you follow a simple package architecture, this should not happen to your components.
Commit: 11e6f28