Really sorry, should be fixed now

Witzig, dass jemand doch mal wieder diese "Sumpf trockenlegen" Parabel auspackt, wo Trump gerade die amerikanische Regierung in einem Sumpf komplett offener Korruption ertränkt hat.

This one: rollupjs.org

Basically this: bsky.app/profile/luka...

The original implementation was rolled back due to some performance issues. This reworks the architecture somewhat.

I definitely have not given up on classes. We just need to make sure that we catch all prototype shenanigans that people might come up with.

Ok, there are quite a few more issues to solve than I expected to make this work, so I will not include this in the initial release, though it would be nice. It is a lot of work to track all usages of a functions return values reliably.

You are right. To be safe, there are quite a few places where we just include the entire object, and return expressions are probably one of them. But this looks fixable to me, will check this later.

Actually, that was a good hint. I found another edge case that I will fix before this is ready. Maybe those variables will be removed after all.

And this is only the beginning. If we find no blockers, next steps will be to bring tree-shaking for dynamic imports to the next level, and eventually allow tree-shaking for classes.

But understand that tools like esbuild, SWC and Turbopack put a lot of pressure on Rollup to improve performance to stay relevant. And projects are getting bigger. At the moment, Rollup sucks for very large projects 😔

I hear you. If you mean patching Rollup itself will be harder, yes, definitely. But the JavaScript plugin system will not change and will remain first class. There may be new helpers for plugins that tap into native code to do things faster, though.