Skip to content
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

Update dependency eslint-plugin-react-refresh to v0.4.16 #1247

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Dec 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-react-refresh 0.4.14 -> 0.4.16 age adoption passing confidence

Release Notes

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.4.16

Compare Source

Fix CJS/ESM interop issue. Sorry everyone for the trouble.

v0.4.15

Compare Source

Add support for custom HOCs (#​60)

By default, the rule only knows that memo & forwardRef function calls with return a React component. With this option, you can also allow extra function names like Mobx observer to make this code valid:

const Foo = () => <></>;
export default observer(Foo);
{
  "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:

import reactRefresh from "eslint-plugin-react-refresh";

export default [
  /* Main config */
  reactRefresh.configs.recommended, // Or reactRefresh.configs.vite for Vite users
];

To follow ESLint recommandations, the rule is added with the error severity.

Some simple types ensure that people typecheking their config won't need @ts-expect-error anymore.

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.


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 was generated by Mend Renovate. View the repository job log.

Copy link

@llamapreview llamapreview bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

All 1 files are either skipped or binary files

Technical Context:

Binary files detected in this PR, which may include:

  • Images
  • Compiled artifacts
  • Binary dependencies

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

@renovate-bot renovate-bot changed the title Update dependency eslint-plugin-react-refresh to v0.4.15 Update dependency eslint-plugin-react-refresh to v0.4.16 Dec 2, 2024
@renovate-bot renovate-bot force-pushed the renovate/eslint-plugin-react-refresh-0.x-lockfile branch from 3b78dd8 to 9a93d6f Compare December 2, 2024 13:13
@ajhollid ajhollid merged commit 43c723e into bluewave-labs:develop Dec 3, 2024
1 check passed
@renovate-bot renovate-bot deleted the renovate/eslint-plugin-react-refresh-0.x-lockfile branch December 3, 2024 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants