As a Halloween thing, I pushed some fake error throwing directly to main for the dev environment, mentioning a 666 http error code. Sadly, I was spotted immediately by a notification complaining about the commit...because of a flaky unrelated test :(

My name is Ian and I approve this message

Don't underestimate Balatro, it can get pretty addictive :D

Something we were wondering at work (a very much for-profit place), was how this will work for "commercial open source projects". Roughly speaking, projects that benefit only the company releasing them, but that happen to be open source. Just putting it on the radar :)

I just checked if we had any exceptions to the rule, but no, unfortunately we do not have full remote positions :(

They definitely might give us a run for the money! I forgot about it!

If Amsterdam, Madrid or Chicago interest you, DM me. Here at Adyen we might just have the largest Vue codebase in the world :O

It's a painful world, where I have to rewrite code to make a test runner happy instead of my users :(

But can you tell Vitest to stop telling me that HTMLElement is not defined?

Would you recommend it to people who, so far, have been happy with just shipping a library with tsc? I've had decent results with just doing that (and not bundling at all), but I'm no expert :D

I should also mention that, funnily enough, it leverages the slot attribute and the template element from the Web Components API. And works with Solidjs too.
The framework convergence is real :D

Simply put, like you guys, I like slots. The teams I work with use preact, but many of the people who joined come from a Vue background, and missed the more declarative way of writing HTML-like code (JSX in this case) with slots as opposed to the imperative way props would be used in (p)react

If you find it useful, we've been using this thing I made github.com/maybebot/nam... in production for a while now. It says preact, but works fine in react as well