[Snyk] Upgrade eslint-plugin-react-refresh from 0.4.7 to 0.4.18 #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade eslint-plugin-react-refresh from 0.4.7 to 0.4.18.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 11 versions ahead of your current version.
The recommended version was released a month ago.
Issues fixed by the recommended upgrade:
SNYK-JS-CROSSSPAWN-8303230
SNYK-JS-NANOID-8492085
SNYK-JS-ROLLUP-8073097
SNYK-JS-VITE-8023174
SNYK-JS-VITE-8648411
SNYK-JS-VITE-8022916
Release notes
Package name: eslint-plugin-react-refresh
-
0.4.18 - 2025-01-11
-
0.4.17 - 2025-01-11
- Fix detection of local components to not generate warning on for variable inside JSX files that follow React component naming (fixes #75)
- Update types to not require extra unnecessary
-
0.4.16 - 2024-12-02
-
0.4.15 - 2024-12-02
import reactRefresh from "eslint-plugin-react-refresh";
-
0.4.14 - 2024-10-24
- Warn if a context is exported alongside a component (fixes #53). Thanks @ IgorAufricht!
-
0.4.13 - 2024-10-19
- Support for
- Support for Arbitrary Module Identifiers syntax (fixes #52)
-
0.4.12 - 2024-09-14
- Support type assertion on default export (fixes #48)
- Add default export to fix usage with jiti (fixes #50)
-
0.4.11 - 2024-08-22
- Ignore type exports (ex.
-
0.4.10 - 2024-08-20
- Support
-
0.4.9 - 2024-07-21
- Support
-
0.4.8 - 2024-07-09
-
0.4.7 - 2024-05-09
from eslint-plugin-react-refresh GitHub release notesESM/CJS interop is the worse that happened to this ecosystem, this is all I have to say.
.defaultproperty access under TS node16 module resolution (fixes #70)Fix CJS/ESM interop issue. Sorry everyone for the trouble.
Add support for custom HOCs (#60)
By default, the rule only knows that
memo&forwardReffunction calls with return a React component. With this option, you can also allow extra function names like Mobx observer to make this code valid:{ "react-refresh/only-export-components": [ "error", { "customHOCs": ["observer"] } ] }Thanks @ HorusGoul!
Add recommended config and simple types (#67)
You can now add the recommended config to your ESLint config like this:
export default [
/* Main config */
reactRefresh.configs.recommended, // Or reactRefresh.configs.vite for Vite users
];
To follow ESLint recommandations, the rule is added with the
errorseverity.Some simple types ensure that people typecheking their config won't need
@ ts-expect-erroranymore.Bump ESLint peer dependency to 8.40
This was actually done by mistake in the previous release when moving from a deprecated API to a new one.
Given that ESLint 8 is officialy end-of-life and the only report (#56) didn't get likes, I'm going forward and documenting the expected minimum version from ESLin in the package JSON so that people can get warning from their package manager.
react-reduxconnect (export default connect(mapStateToProps, mapDispatchToProps)(MyComponent)) (fixes #51)export type foo = string;) (fixes #47)function Foo() {}; export default React.memo(Foo)(#46) (thanks @ SukkaW!)function Foo() {}; export default memo(Foo)(fixes #44) (thanks @ SukkaW!)Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: