eslint-plugin-react-refreshenforces that your components are structured in a way that integrations such asreact-refreshexpect. Limitations ⚠️To avoid false positives, by default this plugin is only applied ontsx&jsxfiles. SeeOptionsto run on JS files.⚠️ ...
Validate that your components can safely be updated with Fast Refresh - eslint-plugin-react-refresh/src/only-export-components.test.ts at main · ArnaudBarre/eslint-plugin-react-refresh
{"plugins": ["react-refresh"],"rules": {"react-refresh/only-export-components":"warn"} } Flat config importreactRefreshfrom"eslint-plugin-react-refresh";exportdefault[{// in main config for TSX/JSX source filesplugins:{"react-refresh":reactRefresh,},rules:{"react-refresh/only-export-compo...
importreactRefreshfrom"eslint-plugin-react-refresh";exportdefault[/* Main config */reactRefresh.configs.vite, ]; Without config importreactRefreshfrom"eslint-plugin-react-refresh";exportdefault[ {// in main config for TSX/JSX source filesplugins: {"react-refresh": reactRefresh, },rules: {"rea...
qdrawmentioned this on Sep 14, 2024 [Snyk] Upgrade: , , core-js, eslint-plugin-react-refresh, react-router-dom, ts-jest, vite qdraw/starsky#1717 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment ...
Validate that your components can safely be updated with Fast Refresh - Release v0.4.12 · ArnaudBarre/eslint-plugin-react-refresh
In typescript-eslint@v8.10.0, they added support for ExportNamedDeclarations having children string literals, due to the 5.6 change of arbitrary module identifiers. These probably aren't supported by HMR anyway, so should they just throw an error? Right now when building for the v8.10.0, ...