Just curious, what’s the benefit of “use” vs throwing a promise?

Yea same, but it doesn’t seem like either of these have been updated super recently or are production ready

Is there a production-grade polyfill yet?

Do you know the status of a production-grade Temporal polyfill?

Still good

Please do

That really went from 0 to ♾️ in four short steps

What kind of tinkering…?

Don’t replace your API with server functions - you lose input validation, middleware, and the ability for other clients to hit your API. Stick with tRPC!

You said you don’t want to hardcode buckets, so you can also use calc() and the vw unit (e.g 50vw) to come up with formulas that apply at different breakpoints

Don’t do this, you can do it all in CSS :)

Media query fundamentals - Learn web development | MDN The CSS Media Query gives you a way to apply CSS only when the browser and device environment matches a rule that you specify, for example

If you have specific percentages your element should take up at different breakpoints, you can use media queries to specify exactly what percentage to take up when you arrive at 400px, 500px, etc.

@media (min-width: 400px) {
.my-class {
width: 50%;
}
}

developer.mozilla.org/en-US/docs/L...

This is such an impressive release. Kudos and thank you!!!

Cute!!! Love this

Totally agreed, this was the magic of the OG getInitialProps API and what made it so great to work with.

Yes it's normal. Every DNS record has a different TTL, and some can be as short as 1 minute. Also, DNS clients can choose to not respect the TTL time and refetch it anyways.

Browsers these days are doing their own DNS lookups over DoH instead of relying on the OS DNS tools, so check your settings.

`react-query-next-experimental` does the same thing as Apollo’s `getDataFromTree`, with the extra super power of Suspense + streaming SSR.

Neither solves the “prefetch data for subsequent navigations” problem.

It _should_ be possible to solve this. DX & not writing queries twice is the hard part.

Great article! I really appreciate the clear guidance at the end.

Oh yikes that's true. They also say on their status page that "some features will remain operational, like installations and search", which clearly was not the case 😬

Scheduled infrastructure upgrade npm's Status Page - Scheduled infrastructure upgrade.

status.npmjs.org/incidents/px...

Looks like npm is doing scheduled maintenance so that probably explains it. I saw pnpm fail to install in a Github Action which is pretty disruptive, but I guess better on a Sunday than a weekday.

@pnpm.io seems to be missing from the npm registry? Is anyone else seeing this?

www.npmjs.com/package/pnpm

I can't wait for neon.tech to run on GCP, because Neon + Cloud Run would be the perfect pairing for autoscaling and branched workflows. Egress fees between GCP and AWS / Azure make this non-ideal currently.

I truly didn’t expect this but @changelog.com Beats are my top 5 songs this year! I put my favorites in a playlist and listened on repeat while coding. They are such great “in the zone” coding songs.

List of unsupported features in Aurora DSQL Unsupported objects Databases - Aurora DSQL supports only one database per cluster at this time. Views Temporary Tables Triggers Types Tablespaces UDFs / Functions other than functions using language = SQL Sequences Unsupported constraints Foreign keys Exclusion constraints Unsupported operations ALTER SYSTEM TRUNCATE VACUUM SAVEPOINT Unsupported extensions Aurora DSQL doesn't support PostgreSQL extensions at this time. The following notable extensions are unsupported. PL/pgSQL PostGIS PGVector PGAudit Postgres_FDW PGCron pg_stat_statements

Is AWS Aurora DSQL really "Postgres compatible" if it doesn't support foreign keys, views, or triggers? 🤔

First time follow, React Summit starter pack!

Isomorphic SSR

@jimmyl.ai What are your thoughts on Next directly supporting this use case of reading headers / cookies in client components on the server?

I know Apollo has been working on something similar but they have the same auth in client components problem.

The auth problem is blocking for sure - I've been able to work around it by storing state in Node globals but it's hacky. Seems like it needs direct support from the Next team to resolve this.