-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Suppress trackTailUpdates if 'true' passed #1386
Closed
brandon-pereira opened this issue
Oct 30, 2019
· 1 comment
· May be fixed by novalina26/anchor#1, TheJ-Erk400/devaccownt#25, TheJ-Erk400/devaccownt#30, kalbroni7/fairy-wallet#2 or kalbroni7/fairy-wallet#4
Closed
Suppress trackTailUpdates if 'true' passed #1386
brandon-pereira opened this issue
Oct 30, 2019
· 1 comment
· May be fixed by novalina26/anchor#1, TheJ-Erk400/devaccownt#25, TheJ-Erk400/devaccownt#30, kalbroni7/fairy-wallet#2 or kalbroni7/fairy-wallet#4
Comments
This was referenced Oct 30, 2019
Fixed in |
This was referenced Aug 30, 2024
This was referenced Sep 5, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The docs say
The warning is informational - it is a notice that this tail update logic is triggered, and does not indicate a problem in the configuration or usage of react-hot-loader.
. I have a team of developers working with me, I'm managing the SSR/HMR setup. I don't think every developer should need to know about the inner works of a HMR. Ideally, I can set setConfig({ trackTailUpdates:true }). to suppress the out-of-bounds warning since it's just informational and not an issue with the configuration. I'd like to keep our console logs to a minimal.Discussion also happening here: #1368
Opening a new issue to track when I create a PR
The text was updated successfully, but these errors were encountered: