Slooooooooowwwwwww ... 🐌

[nelsonic]

Getting multi-second compile and serve times for each page reload where the whole project is recompiled after changing a character in a file ...

internal:dev:  ○ Compiling / ...
internal:dev:  ✓ Compiled / in 7.2s (3782 modules)
internal:dev:  GET /public 404 in 3733ms

Seriously? WTF?! 🤷‍♂️
3+ seconds to serve me a 404 page ...

[nelsonic]

public:dev:  ✓ Starting...
public:dev:    automatically enabled Fast Refresh for 3 custom loaders
private:dev:    automatically enabled Fast Refresh for 3 custom loaders
internal:dev:    automatically enabled Fast Refresh for 3 custom loaders
public:dev:  ✓ Ready in 1780ms
private:dev:  ✓ Ready in 1907ms
internal:dev:  ✓ Ready in 1952ms
internal:dev:  ○ Compiling / ...
internal:dev:  ✓ Compiled / in 7s (3780 modules)
internal:dev:  ✓ Compiled in 517ms (3780 modules)
internal:dev:  GET / 200 in 7802ms

almost 8 seconds to render the homepage ... ⏳ 🤷‍♂️
3780 modules 🤯 what is this project doing ...? 😕

[nelsonic]

Upstream Next.js Dev Mode Slow Compilation: vercel/next.js#48748 475 comments 💬

Who has time to read 475 comments? No wonder they are all using "AI" to summarise ... 😬
Opened over a year ago. Still no solution on the horizon. Not holding my breath that this will magically get fixed. ⏳

vercel/next.js#48748 (comment)

So for a medium-sized project the build times are 20 seconds ... 🐌 😱 #painful

Follow up on Twitter indeed ... 🙃

[GriffinSauce]

@nelsonic please note that table is about migrating a huge app with many quirks, medium sized is incorrect. Also note that CRA is as slow. It's more likely to be a problem with our (mid-migration) code/architecture than with Next.js. Also we're discussing on twitter because I need to keep the traces confidential. Do with that what you want but please don't take a run with my words/data without proper context.

[nelsonic]

@GriffinSauce thanks for the clarification. 👍

Guessing you're referring to https://www.vio.com ?
That does indeed seem like a huge app ... 💭 https://builtwith.com/vio.com 🤯

100+ technologies ... someone got greedy at the buffet. 😜
Product Owner: "We need all the features!"

https://pagespeed.web.dev/analysis/https-vio-com/ytjh3csbrl?form_factor=mobile

Maybe the people using Vio don't use it on the Mobile? 📱 🚫 💭

I remember it as FindHotel.
https://medium.com/viodotcom/findhotel-is-now-vio-com-154c4b9da045

looks like it't going well. 👌

The Nextra site we're building has ~100 pages with a few custom components; nothing special.
It often takes 3-8 seconds to recompile and reload. ⏳
When deployed it's reasonably fast but I'd expect that from a static site. 💭

The Next.js app has hundreds of pages and many custom components
and the engineers working on it are having to do gymnastics to keep it from going slow. 🐌
That probably has more to do with GraphQL than anything else. 🐢
The biggest challenge they are facing is testability! 🧪
Adding features is relatively easy in Next.js / React.js. 🎉
Doing it reliably with good engineering and low latency, not so much. 😕

But again, please don't take my commentary personally, if you're getting your work done with Next.js/Nextra and the people using your product/site are happy, that's all that matters. ❤️

[nelsonic]

Takes more than TEN SECONDS to load a page that has zero changes! 🐌

automatically enabled Fast Refresh ... 😕

indeed ...

How long would slow refresh take? ⏳