[BUG] Module not found: Can't resolve for client components in NextJS 14

[SalahAdDin]

What version of million are you using?

1.0.0-faire.6

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

pnpm

What operating system are you using?

Manjaro Linux

What browser are you using?

Firefox

Describe the Bug

When running our NextJS project after installing Million Lint, the site is not loaded and the console gives us the following issue:

> [email protected] dev /home/luisalaguna/Projects/TRT/twe_fe_next
> next dev

  ▲ Next.js 14.2.3
  - Local:        https://localhost:3000
  - Environments: .env

 ✓ Starting...

 ⚡ Million Lint v1.0.0-faire.6
 - Ingest server: https://localhost:42423

 ✓ Ready in 0.15ms
 ✓ Ready in 4.8s
 ✓ Compiled /src/middleware in 182ms (96 modules)
 ○ Compiling /[locale] ...
 ⨯ ./src/app/_components/navigation/Header/Header.tsx:79:75
Module not found: Can't resolve 'src/app/_components/navigation/Header/Header.tsx'
  77 |     }
  78 |   } else if (module.hot) {
> 79 |     module.hot.accept("src/app/_components/navigation/Header/Header.tsx", () => {
     |                                                                           ^
  80 |       _c();
  81 |     });
  82 |   }

https://nextjs.org/docs/messages/module-not-found
 ⨯ ./src/app/_components/navigation/Header/Header.tsx:79:75
Module not found: Can't resolve 'src/app/_components/navigation/Header/Header.tsx'
  77 |     }
  78 |   } else if (module.hot) {
> 79 |     module.hot.accept("src/app/_components/navigation/Header/Header.tsx", () => {
     |                                                                           ^
  80 |       _c();
  81 |     });
  82 |   }

https://nextjs.org/docs/messages/module-not-found
 GET /en 500 in 10244ms

This only happen to client components.

What's the expected result?

It should run the project properly.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/nextjs-gunq6c

Participation

• I am willing to submit a pull request for this issue.

[github-actions]

Thanks for opening this issue! A maintainer will review it soon.

[NisargIO]

Hi @SalahAdDin, we’ve just deployed a fix for you! Can you try running the setup script npx million@latest. Once it's done, please restart your VSCode/Cursor. Let me know if that works for you!

[SalahAdDin]

Hi @SalahAdDin, we’ve just deployed a fix for you! Can you try running the setup script npx million@latest. Once it's done, please restart your VSCode/Cursor. Let me know if that works for you!

Do I need to sign in to the VS Code extension?

[NisargIO]

Hi @SalahAdDin, we’ve just deployed a fix for you! Can you try running the setup script npx million@latest. Once it's done, please restart your VSCode/Cursor. Let me know if that works for you!

Do I need to sign in to the VS Code extension?

It is not necessary, but for the full experience you will need to

[SalahAdDin]

Hi @SalahAdDin, we’ve just deployed a fix for you! Can you try running the setup script npx million@latest. Once it's done, please restart your VSCode/Cursor. Let me know if that works for you!

Do I need to sign in to the VS Code extension?

It is not necessary, but for the full experience you will need to

Have to check it then!