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
fix(react): improve option for react-refresh #455
Conversation
✅ Deploy Preview for melodious-froyo-4871f8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
allowExportNames: isUsingNext | ||
? [ | ||
'config', | ||
'generateStaticParams', | ||
'metadata', | ||
'generateMetadata', | ||
'viewport', | ||
'generateViewport', | ||
] | ||
: isUsingRemix | ||
? [ | ||
'meta', | ||
'links', | ||
'headers', | ||
'loader', | ||
'action', | ||
] | ||
: undefined, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would allow all of them directly without checking the packages - would that have any bad side-effects?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it should be a big problem, but when using pure vite and react, if the exported name coincides with the preset, it will still affect fast refresh.
I couldn't push to your branch - did you unchecked the "allow edit from maintainer" box? |
Description
Linked Issues
Additional context