Open JakeSidSmith opened 3 years ago
Am I correct in thinking that this package is automatically published when new versions of react/react-dom are released?
Not quite. It's still manual releases and 17.0.1 was released just now 🚀
Is it totally necessary to release a new version for every patch? Surely you'd save a lot of effort by loosening the peer?
That is not under my control. But you don't have to use this library at all, as long as it just applies react-hot-loader "patch" to react. You can do the same via webpack loader.
Another good option is to stop using deprecated React-Hot-Loader and switch to FastRefresh. This time it will not require any extra hack for living.
Thanks, I had no idea there was an alternative. I'll have a look. 😊
@theKashey fyi react 17.0.2 was released, so we need a new bump :)
@theKashey yep, a new release is appreciated. I can't do npm i
without adding --legacy-peer-deps
.
Am I correct in thinking that this package is automatically published when new versions of
react
/react-dom
are released?Currently
react
is on version17.0.1
, but there is only a17.0.0
version of@hot-loader/react-dom
, and since the peer dependency onreact
is strict, you get a warning when installing this package (if using the latestreact
):Is there a specific reason the peer dependency is so strict? Could this be loosened?