Just enabled the elastisearch feature on my @mastohost instance and wow—it hadn’t clicked before but this is a feature that Twitter never had.

I can search my stream**!

(**for folks that have opted in to search)

https://www.epicweb.dev/why-i-wont-use-nextjs from @kentcdodds details some of the very big problems that have been echoing for years through Vercel, Next.js, and React.

Here’s what he listed:

1. Not using The Platform
2. Vendor locked to Vercel
3. Next.js is eating React 🫡
4. Uses experimental features in stable releases
5. Overrides global fetch
6. Complexity in RSC
7. Instability

A good addition to https://www.zachleat.com/web/react-criticism/

@bobmonsour I wonder if you might be interested in providing an API on https://11tybundle.dev/ (just a JSON file that has titles and URLs) that could be consumed by 11ty.dev for community resources? Happy to give proper attribution to your excellent resource too, maybe a heading that says “Community Resources via 11tybundle.dev”?

I’m working on a CMS docs page for 11ty.dev and I’d love to include the resources on https://11tybundle.dev/categories/cms/

Feel free to say no! 😅

Just to be clear, this adds ESM support to all JavaScript files in @eleventy:

• Configuration Files
• JavaScript Data Files (Global, Directory, or Template)
• `.11ty.js` (and `.11ty.mjs`) Template Files
• and importantly we will not require you to upgrade your projects to ESM either. Eleventy 3.0 will continue to support CommonJS Eleventy projects.