u/Middle_Tree_9117

when will react query get a v6? seems like there are new libraries but existing ones are not exactly maintained

can't even update because they broke pages router in 16.4

nice they broke local dev completely with this release

thanks for releasing 16.3! the local dev experience has improved significantly for my team.

1) build cache is now enabled by default for turbopack but when can we actually "trust" it? the build cache for dev was marked as "stable" but we all know that everyone suffered from the memory issues. maybe we should wait until next 17.0?
2) there are still open turbopack issues for dynamic imports related to pages router with no solutions. are we no longer focused on addressing these issues?
3) why is there still no solution for solving the hard navigation between pages -> app router? the incremental migration path is still difficult due to this. easy for new apps or small apps.
4) there are a lot of "experimental" features under next.config that are confusing. optimizePackageImports still says "This feature is currently experimental and subject to change, it's not recommended for production. Try it out and share your feedback on GitHub." yet it has been used by nextjs for a long time. what is the nextjs team currently doing to support experimental features? we never know when they are ready for production usage or not.
5) are there plans to support dynamic variable for dynamic import vs the current full path?

Wow ok I guess I will be charging back chase to make up for the missing credits

Wow! that cherry blossom price is crazy.

yep I agreed. I bought some from REI, and other resellers, and the thickness of the shirts are SO thin.

What is the next/root-params solving? We started moving to cacheComponents but haven’t noticed any issues just yet

Why is the useEffectEvent still unstable?!

how were you able to select seats? I don't see a website for this airline!

Yep, I will try to open one. I did figure out why it is happening but don't know why it is happening only on turbopack. Say I have 3 components,

Component A renders Component B which has an object of 10 dynamic imported components and one of those components render Component C which also has another object of 10 dynamic imported components. Rendering Component C is the culprit. However, if I import Component C within Component A, the issue goes away. I am assuming importing C early will help preload the dynamic imported components or something.. is there some known lazy compiling issue for this scenario locally?

I am getting hydration issue on a page with turbopack enabled and only for dynamic imported components. :/ can't even use turbopack u/timne

https://preview.redd.it/a7vsasvfypaf1.png?width=955&format=png&auto=webp&s=b5f973c9e563d41be6a99749e9e6f59e3968da14

Not worth it at all

Appreciate all the work you do!

My team is constantly asking this question: will there be a day where the page router to app router migration won’t have hard navigation done? It is extremely difficult to manage lost client states on large apps.

Next dev —turbo is taking 90 seconds to compile initially vs 10 seconds with a custom server / webpack 0_0

Damn time to request for a refund.

How do you download the videos from the course?

How? I even got the course just yesterday and came across this thread…