Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove "react-🔥-dom patch detected. You may use all the features." console messages #1173

Closed
stnwk opened this issue Feb 7, 2019 · 7 comments

Comments

@stnwk
Copy link

stnwk commented Feb 7, 2019

Hello :)

It would be nice if we could get rid of this message in the console too:

React-Hot-Loader: react-🔥-dom patch detected. You may use all the features.

It's possible to silence all other console logs, but not this one :/

See

What do you think?

@theKashey
Copy link
Collaborator

Probably it's better to display a message like this when hot patch is not detected, as long as we rely on it.

@a7madgamal
Copy link

how to fix it then?

@theKashey
Copy link
Collaborator

theKashey commented Mar 14, 2019

The current version would display this message only if hot-patch is hot present.

React-Hot-Loader: react-🔥-dom patch is not detected. React 16.6+ features may not work

Cos, you know, 16.6+ features really might not work, especially hooks. React-Hot-Loader is not very reliable thing and might ruin all DX with eeeeaaaasssyyyy 😭. We need some support from React side but have to inject it by ourselves.

@mohsinulhaq
Copy link

38b63cd
This commit said it's supporting 16.8.4, why do we still say it doesn't support 16.6+?
Are there any known issues with 16.6+?

@theKashey
Copy link
Collaborator

@mohsinulhaq - you just linked a common in webpack loader, which is a "react-🔥-dom patch".
There are a few things RHL cannot do from a "user-space" properly. For example, hooks are breaking some internal stuff, and we are injecting additional API into react-dom to actually make them work without surprices.

So - long story short - all the tests are passing with and without hot patch. Everything is about reducing WTF per minute. RHL is a hacky tool by nature - we are hacking things.

@mohsinulhaq
Copy link

Ok understood, so what do you think would be a proper solution? Does something need to change in react-dom officially?

@theKashey
Copy link
Collaborator

reactjs/rfcs#74 - but it's a bit stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants