Kai Cataldo

Upgrading to babel-eslint@11

1

Hi! First of all, thanks for AST Explorer. As a maintainer of ESLint, this tool has been invaluable to my work ❤️ I've been doing some work on babel-eslint, and...

**What version of TypeScript are you using?** N/A **What version of `typescript-estree` are you using?** N/A **What code were you trying to parse?** N/A **What did you expect to happen?**...

Explore using Vite instead of Webpack for asset generation. The current build is quite slow and doesn't progressively re-render/generate its client-side assets, making the development experience slow and painful. Related...

Feature: API to customize Webpack config

1

Similar to the `babelConfig` API, we should add a configuration option that allows you to modify the underlying Webpack config. `webpackConfig()` for consistency?

Feature: Preact support

5

In the spirit of keeping everything as light and fast as possible, we should allow for native support of Preact!

The current marker generation logic takes multiple passes to generate the marker comments for the client-side hydration step. 1. It renders a script tag with the necessary data serialized as...

The 1.0 release has been released and I believe this means we no longer have to use experimental APIs :tada:

This is a WIP. Looks like it all works, but I need to update the `withHydration` HOC to take an options object and serialize this state in the comment we...

Lazy load and hydrate components only when they're in the viewport

1

We may want to put this behind a config option (probably at the component level in [`withHydration()`](https://github.com/kaicataldo/eleventy-plugin-react/blob/main/lib/components/withHydration.js)), defaulting to lazy loading. This will then have to be serialized into the...

For the sake of performance, we should have the generated pages use module/nomodule JS bundles to minimize the amount of JS we're sending to the client.