esbuild

in my old project , using webpack 1.x. And I use esbuild-loader replace babel-loader will print error

` building for production.../Users/wanglihui/WebstoreProject/onionfph5/project/node_modules/esbuild-loader/dist/plugin.js:12
compiler.hooks.thisCompilation.tap('esbuild', compilation => {
^

TypeError: Cannot read property 'thisCompilation' of undefined

I have stories for simple components that work fine. But once I click on a story for a component that uses the next/image component, nothing renders and ladle is broken until reload. Once I clock on a story with next/image the following error occurs in the console:

react.development.js:1309 Uncaught ReferenceError: process is not defined
    at node_modules/next/dist/client/normalize-

GitPod is pretty rad and seems to be a bit ahead of GitHub Codespaces in some ways. I just remote updated some gems and content on a Bridgetown site and previewed it running live—even used Solargraph with Rubocop integration—and it just worked and worked fast. All from my iPad Pro!

So (a) it'd be great to add a bundled configuration so any Bridgetown site can add sup

Where did our docs fail you?

We currently use whatever font sizes the browser provides by default across headings. This is fine, but could cause inconsistent user experiences. We mostly avoided custom sizing because it's so dang hard to configure and scale across breakpoints.

How can we improve?

I saw @AleksandrHovhannisyan's fluid type scale s

Bringing Preact into vitext. That simple.