is this dev mode (npm run dev) or prod mode (npm start/a deployment on e.g. vercel?)

Npm run dev

That's probably why, I experience the same problem and apparently alot of people do too when working in dev environment. https://stackoverflow.com/questions/76408504/nextjs-13-is-insanely-slow-in-dev-environment

Thanks. Now I understand

But is it fast in production?

I just tested, for me it does.

Here's a link that I used to see how to do it: https://shipsaas.com/blog/how-to-run-next-js-build-locally

Thanks ill try it now

I'll

it has been throwing this error since i've tried using npm run build
uncaughtException Error: kill EPERM
at ChildProcess.kill (node:internal/child_process:512:26)
at ChildProcessWorker.forceExit (C:\Users\clint\Downloads\Coding\Nextjs\glamourglow\node_modules\next\dist\compiled\jest-worker\index.js:1:12879)
at Timeout._onTimeout (C:\Users\clint\Downloads\Coding\Nextjs\glamourglow\node_modules\next\dist\compiled\jest-worker\index.js:1:8684)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7) {
errno: -4048,
code: 'EPERM',
syscall: 'kill'

delete .next folder

That's new to hear but worked on more then 10-12 next js projects of 12-14 but never happen can you just check if its No throttling inn network tab

the error above already has its dedicated post https://nextjs-forum.com/post/1243326363168018563, so i'll consider this post resolved

dev mode is always significantly slower than prod mode, regardless of network throttling

Yeah but not that much it take maximum 10 seconds to load

it depends on many things. i have worked on apps where dev server takes 1 min+ to boot before.

👍

Yes

thank you so much for sharing this. @Minskin u just saved my life lmao
managed to solve the memory leak in my M1 macbook air, by adding swcMinify: true in next config

cc: @Clinton401 @joulev in case u guys needed it

Wow, been a while since I posted that. Glad it helped