“I skate to where the puck is going to be, not to where it has been.”—Wayne Gretzky

One year ago, I switched to the Next.js team to work on React 18 and React Server Components support with Jiachi. Happy to see them landed and running as the core of Next.js 13 to empower some of these incredible new features.

5k+ stars and 16k weekly downloads, that was fast! We’ve also made a lot of improvements from 20 contributors in the past weeks :)

github.com/vercel/satori

Same

Introducing Turbopack, the successor to Webpack.

◆ ~700x faster than Webpack
◆ 10x faster than Vite
◆ Native incremental architecture built with Rust
◆ Support for React Server Components
◆ Support for TS, JSX, CSS & more

Now open-source in Alpha.

vercel.com/blog/turbopack

Learn how we built the WebGL experience on the Next.js Conf landing page, leading to almost 100,000 registrations.

vercel.com/blog/building-…

Seems like we’ve made a mistake: it’s not 5 times faster, but 5² times faster...

i have to wrap my head around Shu's satori library. so i can ... render real html + css, and even tailwind, as SVG, and use it anywhere, for instance THREE.SVGLoader. but it's ... not a dead image but reactive. doesn't compute right now. 🤯

codesandbox.io/s/stupefied-pa…

The best part: it’s SVG!

First public status update for my new TypeScript type checker.

kdy1.dev/posts/2022/10/…

Another reason for JSX is that, JSX == parsed HTML & CSS so you don’t have the cost of parsing them again in the runtime (it can be dynamic so can’t be done build time).

But if you have to, you can also pass JSON: `{ type: 'div', props: { ... } }` or use a lightweight parser.

*AppleColorEmoji.ttf