I told it to port a React component to Astro and it starts defining Tailwind classes in my Astro component.
Then it starts creating tons of new components that I never asked to be ported. Then it's way too agreeable and doesn't ask clarifying questions. Going back to writing everything by hand...

I hate it with the power of a thousand suns.
Search engines only show me translated Reddit posts.
Automatically translated YouTube titles make no sense a lot of times.

I have a guess why: The click is triggering a React rerender of most of the page.

🎉

The ones from here: storybook.js.org/docs/writing...

canvas.getByTestId for instance.

I found a utility function that helps here: github.com/storybookjs/...

Here is an example implementation: lit.dev/playground/#...

I thought of compatibility dates because I was reading about how Cloudflare use them. Of course, you could just as well use an incrementing integer. developers.cloudflare.com/workers/conf...

Alternatively, we could have a single version globally and opt into breaking changes by having a version attribute.
e.g. <my-element version="4"> or <my-element compatibility-date="2025-03-12">

They solved this by bundling the web component library for each micro frontend and have the version in the name. So <my-element> becomes <my-element-2-0-0>. This way they can have multiple versions on the same page. Ofc this means a lot more JS.

This was more of a shower thought. I have a customer that uses web components and they have multiple micro frontends on the same page. These micro frontends all use the same web components. Coordinating breaking changes across multiple micro frontends and teams is challenging.

I thought that was a very hairy person for a second.

Can't wait to try Rückenwind 4!

million.dev