ianb.dev
Frontend @adyen Amsterdam
71 posts
162 followers
190 following
Regular Contributor
Active Commenter
comment in response to
post
It's a painful world, where I have to rewrite code to make a test runner happy instead of my users :(
comment in response to
post
But can you tell Vitest to stop telling me that HTMLElement is not defined?
comment in response to
post
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
comment in response to
post
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
comment in response to
post
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
comment in response to
post
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
comment in response to
post
Very excited for Rollsideways!
comment in response to
post
June 13th confirmed.
comment in response to
post
It is, my React friends explained to me it's "just javascript". Maybe you got confused because you use Vue which relies on the other version, unjust javascript 👀
comment in response to
post
{{YouTuber}}
comment in response to
post
Congrats! That's great news! Also a big challenge, now you need to come up with a catchy name for a VoidZero podcast. "On steroids heroes?"
comment in response to
post
See you around then! Loving it so far!
comment in response to
post
But without the @43081j.com username! Which he weirdly enough does know by heart :)
comment in response to
post
I don't know what's coming next, but I have some ideas about what might be coming nuxt
comment in response to
post
Now off to see @jlengrand.bsky.social :D
comment in response to
post
Those charts should also ideally start at 0, not 60. This way it looks a bit misleading to me
comment in response to
post
It's a largish codebase with many contributors so we'd like a standard way of doing things that everyone can adopt and use with ease. Give or take what Pinia does in Vue-world, a relatively simple and slightly opinionated way of how to use reactivity+compostables to handle state management.
comment in response to
post
How do we expose an easy to use global state in contexts like storybook or tests? Is it worth it to look into deep signals?
We have solutions, but we're not sure they're the best ones.
comment in response to
post
If we start using "stores" as hooks will we end up regretting it because of hooks rules or is it ok to (potentially needlessly) call the hook on the top of a component? For migration purposes what's the best way to ensure existing re-renders do run till we're confident to not have them run?
comment in response to
post
Just getting started so I cannot give a very insightful or thought out answer, but we're looking for patterns to mainly address shared state. Do we use Context, or closures, or a singleton pattern? Is it ok to just export a signal from a plain TS file without wrapping it in a function?
comment in response to
post
That's great to hear! Looking forward to it, thanks :)
comment in response to
post
I just wish there were more resources about best practices and/or foot guns, especially regarding handling global state. Any links appreciated #preact #signals
comment in response to
post
No promises, but I'll try :)
comment in response to
post
That's amazing. The library I work on outputs 8+ bundles in a relatively convoluted way. With the Vite6 Environment API and this, we'll be able to simplify it so much, love it! (node18 is EOL in April too, which makes things even easier)
comment in response to
post
Does this mean libraries will no longer need to output a cjs bundle? (if supporting only node20+). Impressive job indeed, love it when things get backported :)
comment in response to
post
Mainly because less people want or need to learn a build tool, so ads and courses bring less revenue. Now the author, @evanyou.me, partnered with other OSS authors and investors to found Void0, a company promising a new generation of unified frontend tooling
comment in response to
post
Vue is an interesting one. Roughly as widespread as Angular, but not backed by any big company, but a rare case of financially successful OSS (Ads and courses).
Ironically, the author then proceeded to create Vite, a build tool arguably even more widespread, but financially way less viable
comment in response to
post
I work on the frontend for "Adyen components", docs.adyen.com/platforms/co..., our embeds/sdk that our merchants can use for things like checkout, onboarding for platforms and general platform info. Since they should feel seamlessly part of the merchants website, we do our best to white label them
comment in response to
post
The stock market reads your posts!
comment in response to
post
Interested! Let me know :)