Seems like Maps are serializable by React so no need to fix those.

Apparently “use cache” doesn’t persist across builds so that’s a big cause for the many writes. Wonder if they’ll enable Data Cache for “use cache” later.

Might reduce use of generateStaticParams and use “use cache” more sparingly

Discarded the excluding of updatedAt fields, not worth. Gonna find a sane solution for the “use cache” stuff and make sure all cached stuff is serializable (I’m returning some Map instances a few places) and then check if things improves

I just want to build and do things the right way, but I don't know if I'm doing it right or not.

I've done `next build` twice in a row and try to compare the builds with an AI generated (obv) script. A bunch of `createServerReference` and `registerServerReference` diffs, so not sure if they count

Happy new year! Next.js/Vercel doesn't want me to have nice things though bsky.app/profile/kjet...

Next.js told me I used new Date() in functions returning Prisma data (so lies) so I threw in a bunch of "use cache" and now my comparison script tells me I have like 500 more diffs.

I'm wondering what kind of hell this is. Why am I spending time on this and why aren't there better tools

An earlier boss got me en.wikipedia.org/wiki/What_If.... Nice nerdy gift :)

Nearly 4x improvement locally though..

As mentioned in the issue there exists a rule called no-implicit -coercions which can disallow shorthands like +foo but then you would just change it to Number(foo) and have the same problem as before