Eslint rule no-async-client-component doesn't work
Open
Nobody has claimed this yet.
Linting
- Dominant language
- JavaScript
- Stars
- 142k
- Forks
- 32.5k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 351
Description
Link to the code that reproduces this issue
https://github.com/ThomasKientz/next-eslint
To Reproduce
- Run
npm run lint
Current vs. Expected behavior
I expected ESLint to output the error
"no-async-client-component"
instead, ESLint outputs
No ESLint warnings or errors
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T8122
Available memory (MB): 16384
Available CPU cores: 8
Binaries:
Node: 20.14.0
npm: 10.7.0
Yarn: N/A
pnpm: 10.5.0
Relevant Packages:
next: 15.2.3 // Latest available version is detected (15.2.3).
eslint-config-next: 15.2.3
react: 19.0.0
react-dom: 19.0.0
typescript: 5.8.2
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Linting
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction repository at https://github.com/ThomasKientz/next-eslint and run npm run lint using the reported Next.js 15.2.3 environment. Trace why the no-async-client-component rule produces no diagnostic, then confirm that linting the reproduction reports the expected error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, nextjs, react
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100