ArnaudBarre/eslint-plugin-react-refresh
### [`v0.4.1`](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#041)
[Compare Source](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.0...v0.4.1)
- Ignore `export type *` (fixes [#12](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/12))
- Support for all-uppercase function wrapped in forwardRef/memo ([#11](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/11))
### [`v0.4.0`](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#040)
[Compare Source](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.3.5...v0.4.0)
##### Add `allowConstantExport` option (fixes [#8](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/8))
This option allow to don't warn when a constant (string, number, boolean, templateLiteral) is exported aside one or more components.
This should be enabled if the fast refresh implementation correctly handles this case (HMR when the constant doesn't change, propagate update to importers when the constant changes). Vite supports it, PR welcome if you notice other integrations works well.
##### Allow all-uppercase function exports (fixes [#11](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/11))
This only works when using direct export. So this pattern doesn't warn anymore:
```jsx
export const CMS = () => <>>;
```
But this one will still warn:
```jsx
const CMS = () => <>>;
export default CMS;
```
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
^0.3.4
->^0.4.0
Release Notes
ArnaudBarre/eslint-plugin-react-refresh
### [`v0.4.1`](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#041) [Compare Source](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.4.0...v0.4.1) - Ignore `export type *` (fixes [#12](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/12)) - Support for all-uppercase function wrapped in forwardRef/memo ([#11](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/11)) ### [`v0.4.0`](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/blob/HEAD/CHANGELOG.md#040) [Compare Source](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.3.5...v0.4.0) ##### Add `allowConstantExport` option (fixes [#8](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/8)) This option allow to don't warn when a constant (string, number, boolean, templateLiteral) is exported aside one or more components. This should be enabled if the fast refresh implementation correctly handles this case (HMR when the constant doesn't change, propagate update to importers when the constant changes). Vite supports it, PR welcome if you notice other integrations works well. ##### Allow all-uppercase function exports (fixes [#11](https://togithub.com/ArnaudBarre/eslint-plugin-react-refresh/issues/11)) This only works when using direct export. So this pattern doesn't warn anymore: ```jsx export const CMS = () => <>>; ``` But this one will still warn: ```jsx const CMS = () => <>>; export default CMS; ```Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.