TL;DR
Yes, I understand that you will immediately have doubts about what I am saying, because "How can you change what Spotify, OpenAI a...
For further actions, you may consider blocking this person and/or reporting abuse
You do realize that this is deceptive, right?
The folder size on your device might be smaller, but you still have to load resources from the URLs when the page loads.
Plus, the actual output of a Next.js build is much smaller than the size of the folder. Dependencies are tree-shook, compiled, minified, etc.
Peak find 🔍
Hello! The fact that the
script's are connected like this does not give anything. I am not going to lie about this - it is pointless. If I had installed them it would have been not 3.6mb, but 3.7mb - it would not have changed anything. As for the Next.js assembly, I do not argue, it is not 300 mb, but it also weighs normally. Imagine, one normal application has about several thousand modules, to make a normal site - this is literally gigabytes of disk space.Thank you very much for your comment! I changed the code and loaded the modules. It turned out to be 4.4mb instead of 3.6mb, so that there would be no feeling that I was misleading. This topic has been discussed for a long time on Alpine.js and HTMX, you can take their examples. There is no point in repeating myself. This is only a possible alternative in some tasks.
Wow, been thinking about framework bloat myself - you actually switched it up and got a lean setup, respect.
Thank you! Yes, modules bloat the project a lot.
Are you a a bot? I see you commenting on every post LOL
Love seeing someone actually ditch the usual framework bloat and prove it works - makes me rethink SSR vs CSR for my smaller projects. Curious, what limitations did you hit with HMPL compared to Next.js in a real-world scenario?
If it worked in 2010 why shouldn't it work in 2025? What's to prove here?
Serious projects like Spotify will be very difficult to build, but simple landings and modules for real projects are quite possible. That's the difficulty.
Great breakdown of the early experience with Next.js—especially the realistic look at how quickly project size can escalate even before significant development begins.
[ I appreciate the honesty around installation weight and the practical insight into what happens when you start adding state managers like RTK Query or building more components. It’s something many devs overlook until the project starts ballooning.
Refer Style Guide - Click here ](rkoots.github.io/styleguide/)
Well! This is interesting.
I think so too :)
I recently moved to NextJS (fully) and just posted nextjs pros over reactjs. And just after I got yours this post. Another minor shift to use this new module ig 😄.
Good article! Web components are also said to be good
Thank you! Yea.
Nice!
Good discussion! Thank you for your effort.
excellent work
Thanks!
Good information provided
In fact, the result is quite surprising to me for small applications.
Good discussion! Thank you for your effort.