ianb.dev
Frontend @adyen Amsterdam
45 posts
137 followers
173 following
Regular Contributor
Active Commenter
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 :)
comment in response to
post
Americares is delivering hygiene kits, N95 masks, medicine, safe drinking water, and other critically needed aid for survivors.
Additional donations made through our payment partner, Adyen, will also be matched in an effort to make wildfire relief contributions go even further.
comment in response to
post
The person on the left is not amused.
comment in response to
post
We also have @pi0.io , @thealexlichter.com in Vue/Nuxt ecosystem and @kilianvalkhof.com of Polypane. Lots of interesting tech people here in the Netherlands :)
comment in response to
post
There are some feeds, but not so intuitive/straightforward, Burton mentioned them yesterday
bsky.app/profile/stuf...
comment in response to
post
It states in the docs, it took a great deal of inspiration from tanstack query, but for Vue
pinia-colada.esm.dev/why.html#Com...
comment in response to
post
The bird is no longer the word 🦋
comment in response to
post
Never managed to get anything other than 1.0.0 :D This is a stackblitz where I installed the cem analyzer in a Lit starter, and the manifest ends up with a 1.0.0 schemaVersion 🤷
comment in response to
post
I never even wanted to be on X, but it's a means to follow the people I want to hear from. Bluesky seems like a cleaner, nicer experience and I like the idea of the AT protocol. And I won't lie, it's also a moral/political choice for me
comment in response to
post
Can the CEM analyzer generate a newer schema? The latest one is 2.1 but the analyzer seems to build only 1.0
comment in response to
post
Shiki is 🔥
comment in response to
post
As a prolific author of many libraries, would you have some recommendations on resources where to learn how to ship good ones?
At work we have one that could use some love, and I'd really like to improve it
comment in response to
post
It's ok to support both commonJS and es modules, but esm(.dev) is the future 😁
comment in response to
post
You have this podcast about Vue on baky if you want @dejavue.fm 👀
comment in response to
post
We need some 🦋 exclusives like Vitepress @brc-dd.bsky.social
comment in response to
post
Italian edition of "Programming in PHP" :D I even found some printed out pages of the PHP documentation website at my mother's place, since as a kid I had limited internet time