I have this app which is running in NextJs 4.22 . It launches sometimes but most of the times it doesn’t launch as expected when I run it through Replit console button. Anyone else facing similar issues ?
$ npm list next
my-app@0.1.0 /home/runner/ProjectName
├─┬ next-auth@4.22.1
│ └── next@13.4.7 deduped
└── next@13.4.7
Adding logs as comments I am not able to edit the post:
npm run dev
> my-app@0.1.0 dev
> next dev --hostname 0.0.0.0
(node:3059) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
- ready started server on 0.0.0.0:3000, url: http://localhost:3000
(node:3070) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
- event compiled client and server successfully in 356 ms (18 modules)
- wait compiling...
- event compiled client and server successfully in 167 ms (18 modules)
Hi @KiranVadakkath thanks for your post and welcome to the community!
Could you please provide some more information? If possible a link to the Repl you are working on would help as it would let others in the community suggest some ideas.
Create the same app with stock nextjs template (next@13.4.9) of replit and it worked. If you upgrade the next js version of a project then run won’t work, i think it is a bug.
We aren’t able to reproduce this issue. How are you upgrading the NextJS version in the newly created project? Could you create a NextJS Repl and configure it to reproduce the issue, then send it to us so we can investigate?
It runs fine now on NextJS12. If I uninstall NextJS12 and install NextJS13 using npm then it fails to run.
The logs I get when the NextJS13 fails to run look the same as Kiran’s. It just hangs there and then I get the “Hmm… We couldn’t reach this Repl” message