erika.florist
Editor tooling at @astro.build, and other stuff, sometimes. Core maintainer on https://volarjs.dev
https://erika.florist
94 posts
1,026 followers
89 following
Regular Contributor
Active Commenter
comment in response to
post
It pains me in most oop languages
comment in response to
post
Excited for the Rust package to be published officially so that it's usable outside of WASM too 😄
comment in response to
post
A little bit messy, but it was this specific commit: github.com/Princesseuh/...
The issue happens with the official example repo as well once you update the dependencies (and you get another error if you don't, ha)
comment in response to
post
Similarly, tools like Volar will increase the similarity of how framework-specific formats like .vue, .svelte, .jsx and .gjs/.gts *behave* in our editors.
comment in response to
post
No, we just sent the request again and it worked
comment in response to
post
Installing `tsx` into your repo and having a npm script that you run with `node --run {script_name}` instead of using `npx` should help a fair amount!
comment in response to
post
I am, I just switch between TypeScript at work and Rust in my spare time
comment in response to
post
I wish CMSes could adapt to my content more. They all feel really generic and not extendable in the ways I'd expect
For instance, to power erika.florist/catalogue/ I wanted to have a CMS where I could have a button that fetches the data of the media I'm adding, but it wasn't possible
comment in response to
post
oh gosh it has incremental builds
comment in response to
post
🤨
comment in response to
post
Mine is if `docs` lead to the Astro docs or something else
comment in response to
post
First they had `vue`, fully-featured, but perhaps a bit heavy, so they made `petite-vue`, for those looking for smaller sizes.
And now you're telling me there's a `zero-vue`? 🫣
comment in response to
post
for sure, I think what Rust is lacking is probably a better way to handle publishing, something similar to changesets in the JS ecosystem. Anything to reduce the friction of publishing would help!
comment in response to
post
Looks great
comment in response to
post
I'm 3/4 in success for context, waiting on @rolldown.rs now, but that one is still early enough that it's a little more understandable that it isn't published yet
Unfortunate that there's no real solutions to work around this in the meantime
comment in response to
post
Hmm, I already follow some people whose content I don't particularly enjoy just so the timelines could theoretically be better. Not sure I'd be able to fit many more people in there, ha.
comment in response to
post
I believe it worked with await but it was more cumbersome to use image inline
`<Image src={await import("...")} />` bit long
comment in response to
post
I made it support that so that it was easier to use in MDX especially, but it's great all around
comment in response to
post
oh gosh it can output pages
comment in response to
post
Still on the fence on whitespace sensitivity
comment in response to
post
That's cool, awesome work
comment in response to
post
Which tools do you mean by "the existing tools"?
comment in response to
post
Preact and Solid both uses class, it's a choice from the React team to use className at this point
comment in response to
post
Glad you like it! It was one of my favorite things to work on this major.