I asked this same question at the next.js conference a they said yes for, use cache:remote at least.

Interesting! I have it caching with dynamic parameters in my very recently released cache-components redis handler. I didn’t even try the behavior in vercel.

github.com/mrjasonroy/c...

Makes sense. Curious though, are you wrapping those random things in suspense and they are using “use”? Is that where the promises resolve?

The model wants you to move that logged in state fetch further down the tree, wherever it is needed. It makes you ask “does the root provider need user login?”

How much money wasted??? No fault on the injury but it wasn’t like it was going to go well unless things were perfect.

In general if it doesn’t run on node honestly I’ll probably skip it unless it’s business critical.

Lots of junior devs in “far off lands” insulated from social interaction and influenced by the flavor of the day because they don’t have experience building things or working with people.

Just maintaining their local plumber and church websites for clients that hate them.

Ha. I just have very similar experience of people I have known - crust punks, ar-15 kind of racist conservatives, weed farmers, crystal healers and off the land folk all converging together to have horrible, horrible converging opinions.

Hmm, I haven’t…. That’s a good idea though. I’ll see what I can setup. We use cloudflare zerotrust so I’ll see what is possible.

I imagine this is an issue for lots of people behind private network APIs not connected to the internet (sometimes behind AWS SSO sessions too)

But none of this works if you need to access things over a VPN or through tunnels… I can’t get web versions to make the requests to internal dev URLs secured through short lived VPN connections. I never fully yolo anyways but get close, letting it modify vault secrets even. Too cumbersome!

It won’t be an alpha/beta feature after Wednesday.

Yep! It’s the return of the PMs and well defined tickets :)

You learn the language over time. Simple, well directed instructions with specific directions where to start an learn from help a lot.

It will change code. We’ll end up with a lot of markdown for LLMs colocated with files.

Let me guess, his family history in Argentina goes back to about 1945…

I’m around 60. It only works well with tests… it is better at writing unit than E2E or integration tests but that makes sense.

I do wonder why affect it will have on languages things are written in. Which are better for AI? Typing seems essential, and popularity of the language is important.

For us, we have a React Context provider that includes "use" and "useOptimistic." fireEvent and act sometimes caused render errors, though they may be fixed now. We had to use a lot of tricks in react-testing-library to get React not to complain or tests to fail, see my response to @kentcdodds.com.

Yep, that's how we use it, and found it more reliable. We were getting React render errors otherwise.

Here's a fun one: We also have to wrap the render in an async act() too - "useOptimistic" and "use" in the provider.

Take out that pesky await (that ESLint doesn't like) and it all breaks.

I found that the userEvent wrapper really helps with testing anything with transitions.

Maybe… all the crap we write and do in things like performance reviews, emails, introductions to PRDs, marketing copy, etc. don’t matter at all. We can get the work done without all of that and institutions, training, people and efforts that go into it.