Skip to content

fix: support ESLint 10 flat config in build hook - #25

Draft
Cherry7593 wants to merge 1 commit into
react-component:mainfrom
Cherry7593:codex/eslint10-flat-config
Draft

fix: support ESLint 10 flat config in build hook#25
Cherry7593 wants to merge 1 commit into
react-component:mainfrom
Cherry7593:codex/eslint10-flat-config

Conversation

@Cherry7593

Copy link
Copy Markdown

What changed

Remove the obsolete --ext .tsx,.ts CLI option from the build hook's ESLint invocation.

Why

The current package uses ESLint 10 flat config, where --ext is no longer accepted. This makes consuming rc-component package builds fail before Father compilation.

The target directory and dynamically injected @typescript-eslint/consistent-type-exports / restricted internal import rules remain unchanged.

Validation

  • father-plugin lint passed
  • father-plugin Father build passed
  • pristine rc-image lint, TypeScript 6 typecheck, 80 tests, ESM/CJS/declaration/Less build and package output passed
  • an intentional @rc-component/motion/es import was still rejected and failed the consumer build

No runtime API changes.

@coderabbitai

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9adc8c8b-1515-4b97-bc8b-071d72bfa75a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for freeto 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.

1 participant

@Cherry7593