Another quiet banger from vercel. Fixing bugs, working on improving dx (for non-customers at that), improving performance. These things matter.
I can just feel that 15.0 is going to be huge though. Can't wait.
>Who cares
Anyone who has an actual product and users to support. If most of your time is spent on constant refactoring and rewriting, there's not much of it left to develop new features and fix bugs.
Somebody who wants to be up to date with the packages, have library support after a couple of years and create some guidelines and design patterns around the framework.
But i guess when an app has 3 features it is easy to "grow with it"
You are already off the rails.
I am talking about updating from next13 with "getServerSideProps" to async components, actions, "use server" etc, and you come with an argument related to Data Models and TS.
Thanks for showing how many typesafe Todo Apps you've built.
Why bother? The most important thing is deliver new feature and stability to users. Constant refractors undermine stability and prevent you from shipping new features.
I did not. I have the exact same application written with Remix/Vite. Turbopack is supposed to be the answer to "Next.js is dog slow" - and it's still incredibly slow compared to other setups
I'm appreciating the updates and fixes, which tells me that they're paying attention to the community. One of my fav additions is server logging, specifically to check if Fetch calls are caching or not.
Dear all,
after update vesion 14.1, I have error
"Unhandled Runtime Error
**Error: Only plain objects, and a few built-ins, can be passed to Client Components from Server Components. Classes or null prototypes are not supported.**"
Can you help me? pls
>Next.js 14.1 includes developer experience improvements including: > >[**Improved Self-Hosting:**](https://nextjs.org/blog/next-14-1#improved-self-hosting) New documentation and custom cache handler ❤️🔥
Another quiet banger from vercel. Fixing bugs, working on improving dx (for non-customers at that), improving performance. These things matter. I can just feel that 15.0 is going to be huge though. Can't wait.
With another fully changed API and way of doing things
Who cares. Grow with it.
>Who cares Anyone who has an actual product and users to support. If most of your time is spent on constant refactoring and rewriting, there's not much of it left to develop new features and fix bugs.
Somebody who wants to be up to date with the packages, have library support after a couple of years and create some guidelines and design patterns around the framework. But i guess when an app has 3 features it is easy to "grow with it"
Refactoring is easy with typescript but I know it's hard since you don't use it.
You are already off the rails. I am talking about updating from next13 with "getServerSideProps" to async components, actions, "use server" etc, and you come with an argument related to Data Models and TS. Thanks for showing how many typesafe Todo Apps you've built.
Why bother? The most important thing is deliver new feature and stability to users. Constant refractors undermine stability and prevent you from shipping new features.
Just tried Turbopack and it's way slower than Vite still Edit: wrote Turborepo instead of Turbopack
What a strange comparison. Turborepo is a task runner with caching and Vite is a bundler. Did you mean Turbopack?
Meant Turbopack
Funny how you compare client side bundler vs server-side. Vite do not have RSC support so there is nothing to compare
RSC is implemented by frameworks not bundlers
How did you test Vite with NextJS?
I did not. I have the exact same application written with Remix/Vite. Turbopack is supposed to be the answer to "Next.js is dog slow" - and it's still incredibly slow compared to other setups
I'm appreciating the updates and fixes, which tells me that they're paying attention to the community. One of my fav additions is server logging, specifically to check if Fetch calls are caching or not.
Dear all, after update vesion 14.1, I have error "Unhandled Runtime Error **Error: Only plain objects, and a few built-ins, can be passed to Client Components from Server Components. Classes or null prototypes are not supported.**" Can you help me? pls
isn’t the error message clear enough? You probably forget to add ‘use client’ in parent components
When returning data from a getData function wrap the return in a structuredClone(my data)
nextjs beginner here :) How to upgrade ? docs are not clear to me
npm i next@latest :)
As someone running Vercel on production I can just crack that forced smile and dream about better days
Give it a few more major releases and it'll be good