react

react copied to clipboard

v0.4.20

Compare Source

• Don't warn on nested HOC calls (fixes #​79)
• Fix false positive with as const (fixes #​80)

v0.4.19

Compare Source

Add name to configs for ESLint Config Inspector

v0.4.18

Compare Source

ESM/CJS interop is the worse that happened to this ecosystem, this is all I have to say.

v0.4.17

Compare Source

• 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 .default property access under TS node16 module resolution (fixes #​70)

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.

v0.4.14

Compare Source

• Warn if a context is exported alongside a component (fixes #​53). Thanks @​IgorAufricht!

v0.4.13

Compare Source

• Support for react-redux connect (export default connect(mapStateToProps, mapDispatchToProps)(MyComponent)) (fixes #​51)
• Support for Arbitrary Module Identifiers syntax (fixes #​52)

v0.4.12

Compare Source

• Support type assertion on default export (fixes #​48)
• Add default export to fix usage with jiti (fixes #​50)

v0.4.11

Compare Source

• Ignore type exports (ex. export type foo = string;) (fixes #​47)

v0.4.10

Compare Source

• Support function Foo() {}; export default React.memo(Foo) (#​46) (thanks @​SukkaW!)

v0.4.9

Compare Source

• Support function Foo() {}; export default memo(Foo) (fixes #​44) (thanks @​SukkaW!)

v0.4.8

Compare Source

• Support export const foo = -1 with allowConstantExport (fixes #​43)

v0.4.7

Compare Source

• Support export { Component as default } (fixes #​41)

v0.4.6

Compare Source

• Ignore cypress test files (#​39)

• X
• Mastodon
• Reddit
• LinkedIn

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.