Silent failure when running npm run dev

[CodyMoore240]

Verify canary release

• [x] I verified that the issue exists in the latest Next.js canary release

Provide environment information

> test-app-three@0.1.0 info
> next info

    Operating System:
      Platform: win32
      Arch: ia32
      Version: Windows 10 Home
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.4-canary.8
      eslint-config-next: 13.2.3
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

https://github.com/CodyMoore240/test-app-three

To Reproduce

run npm install run npm run dev

Describe the Bug

upon running npm run dev, this is displayed in the console and then silently fails

test-app-three@0.1.0 dev next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000

Expected Behavior

It should not silently fail and run the project

Which browser are you using? (if relevant)

Chrome 110.0.5481.178

How are you deploying your application? (if relevant)

No response

[OlegLustenko]

Could be related? https://github.com/vercel/next.js/issues/46884

It's not failing but taking life-long time?

Worth checking this recommendation: https://github.com/vercel/next.js/issues/46884#issuecomment-1460906417

[CodyMoore240]

I tried the solution provided in #46884 and got the following output:

> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
warn  - You have enabled experimental feature (swcFileReading) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.`

Still the same silent failure.

[singhinder2]

getting same error. npm run dev fails on v13.2.4

[OlegLustenko]

Just curios here, should be some --verbose command for seeing logs? Or anything?

[nakamann]

I had the same problem, removing the swcPlugins: [['next-superjson-plugin', {}]] line from the config helped me

[singhinder2]

downgraded to 13.1.6 for the time being

[baocancode]

I had the same problem. Removing swc-plugin-coverage-instrument does make it work again for my code. Downgrading to 13.2.3 for now (need to delete .next directory before running next dev).

[SD-Gaming]

I follow the official doc and find this issue.

When I run dev, the CLI quit after a while, and no error is displayed.

I downgrade to 13.1.6 is OK, but I must remove import 'next/font/google'.

---

Append:

I upgrade the latest canary and switch to x64 nodejs, and the issue disappears.

   Operating System:
       Platform: win32
       Arch: x64
       Version: Windows 10 Pro
     Binaries:
       Node: 18.15.0
       npm: N/A
       Yarn: N/A
       pnpm: N/A
     Relevant packages:
       next: 13.2.5-canary.13
       eslint-config-next: 13.2.4
       react: 18.2.0
       react-dom: 18.2.0

[CodyMoore240]

For me this was solved by using a windows system with the x64 architecture.

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.15.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 13.2.4-canary.8
  eslint-config-next: 13.2.3
  react: 18.2.0
  react-dom: 18.2.0

[singhinder2]

I'm already using windows x64 It seems to be an issue with node v18.15.0. I downgraded to v17.9.1, didn't face this issue. Also, upgraded to v19.8.1 no issue there as well

[baocancode]

Maybe related to https://github.com/vercel/next.js/issues/46989, which I think will be resolved soon.

[Konadu-Akwasi-Akuoko]

Downgrading to next version 13.4.1 helped

[eraybay]

idk if it can work for everyone but I just re-reloded the localhost link in my browser and it worked