reinhold.is
Open Sourcerer at @chromaticui.bsky.social working on @storybook.js.org 📚
Write stories. Not too many. Mostly Svelte ones.
🙋♂️☀️⚓🌱🙋♀️
371 posts
1,000 followers
460 following
Regular Contributor
Active Commenter
comment in response to
post
That horse completely threw me off.
If you hadn't lifted your hands I wouldn't have suspected a thing. 😅
comment in response to
post
Damn mister travel man!
comment in response to
post
Oh wow thats pretty impressive!
comment in response to
post
Oh wow TIL! Thank you! Cunningham's Law never disappoints.
comment in response to
post
what's the use case for users importing directly from dist-files, instead of relying on the export map? That seems like an anti-pattern to me.
minimatch even has the correct export maps set up for this today. github.com/isaacs/minim...
comment in response to
post
Based on the issue it looks to me like they want to dual publish, so its about exposing both formats to the user, which sounds like an exports thing to me?
If its really about internally cross-referencing modules and not about what the package exports, that's a perfect use case for .mjs and .cjs
comment in response to
post
Multiple package.json files in package subpaths is not a thing, that sounds like a huge misunderstanding of the spec.
This is exactly what the export conditions are made for.
comment in response to
post
thank you, it was an absolute pleasure to meet you! I didn't know what to expect from an arctic animal, but you blew all expectations in both wit and kindness.
comment in response to
post
That plugin is the GOAT of debugging
comment in response to
post
Oh no I want all of these!
comment in response to
post
Do you have an NVR too then? That's the upfront cost that's annoying me.
comment in response to
post
Could be a good middleground, but I already have Ubiquiti network, so I don't think it makes sense for me personally.
comment in response to
post
YouTube Ads IS your therapist now.
comment in response to
post
It all starts with handing out holo stickers at a tech conference. Not exactly sure what the next step is though.
comment in response to
post
oh this is cool. fantastic way to explain the concepts.
comment in response to
post
One vs multiple refs is a good point.
And I had forgotten about the whole thing with referential equality shenanigangs
comment in response to
post
Ah yeah I figured reactivity would be nicer in Svelte.
comment in response to
post
bind:this matches useRef I think (?), I'm talking about the lesser known callback ref style
tkdodo.eu/blog/avoidin...
comment in response to
post
Virtual tickets are still available. 🙂
www.sveltesummit.com/virtual-ticket
comment in response to
post
No it's only too much when it starts tasting bad.
comment in response to
post
You're going to end up on some testimonial page somewhere.. 😅
comment in response to
post
Ha nice!
comment in response to
post
You're absolutely right.
bsky.app/profile/rein...
comment in response to
post
Oh wow, great!
Someone should write a guide/blog post on how to set all of this up, looks simpler than I had imagined! 👀
comment in response to
post
Oh wow, great!
Someone should write a guide/blog post on how to set all of this up, looks simpler than I had imagined! 👀
comment in response to
post
So you're just using Vite's library mode to compile the Svelte component?
github.com/LoopbackApp/...
And consumers can import the JS, and nothing else?
Why iife? 🤔
comment in response to
post
Ah cool. Then I'm interested in hearing more about "Another Svelte package depends on that and generates a web component."
comment in response to
post
How do you consume it then? Does that require Svelte too?
comment in response to
post
Yeah I dont think anyone have really solved cross framework SSR yet. Other than maybe Astro, but that's not really viable as a cross framework UI lib.
comment in response to
post
Damn that's a niche market to serve for them.
Impressive if that's sustainable!
comment in response to
post
Haha sounds wild
comment in response to
post
What are you speaking about? 🙂
comment in response to
post
If people want to dismiss Svelte because they dont like the syntax or paradigm I think that's totally fine, but it's a shame when it's because of tooling.
I'd think something like this would make sense as a "mode" in svelte-package
comment in response to
post
The demand for building framework agnostic UI libs is increasing, and I think Svelte is in a perfect position to capitalize on that with the web component output.
Unfortunately today, I think it's fair to dismiss it as viable just because getting the build setup right is _really_ hard.
comment in response to
post
Ah YES, that was exactly what I was looking for! 😅
I'm not afraid of buggy code, in fact I work with it every day!
comment in response to
post
good question! CSF is short for Component Story Format. That is what we call the format/syntax that you write Storybook stories in: storybook.js.org/docs/7/api/csf
For Svelte, we have a special dialect for it that we call Svelte CSF, which is implemented in the addon mentioned.
comment in response to
post
Haha what.
Could it be a MAC address collision?
comment in response to
post
Yeah the original idea was to abstract it out, but we ran out of time. 😔
It also ended up relying on internal data structures, but I think the end result would be valuable a lot of other places!
Always happy to chat about it. 🙂