scottspence.dev
🤝 Svelte Society London co-founder
🧡 Svelte ambassador
📔 I blog what I learn over on scottspence.com
📈 Engineering lead at XtendOps
🛠️ Building skykit.blue
📍 UK
1,520 posts
2,853 followers
1,930 following
Regular Contributor
Active Commenter
comment in response to
post
Ah cool! The design system is legit
comment in response to
post
Cool! Gov uk was react last time I was working with them (2018 😅)
Does the brand refresh include switching to vue?
comment in response to
post
Thanks man, been an “on the side” thing for the last couple of weeks now, really helping out with working on the migration we’re doing
comment in response to
post
I've always used an API key for Clause code, didn't know there were restrictions?? 🤔
I don't really use it heavily though as I find it clunky to use
comment in response to
post
Ok, so I guess you're thinking up your own use case for this (the original post), but, just bear in mind I didn't mention MCP
comment in response to
post
I made a GitHub action for migrating from Svelte 4 to Svelte 5 if you're interested
bsky.app/profile/scot...
comment in response to
post
Yeahp!
Claude 4 is a lot more capable if you're asking me, but yeah, a concise rules file for Cursor/Windsurf was all I really wanted
The docs feature in Cursor id pretty good though, so, my thought was point the docs to the llms.txt file and away we go! 😊
bsky.app/profile/did:...
comment in response to
post
Just had to check the keyboard to see how far away those two letters were 👀
comment in response to
post
Yes! THAT would be awesome!!
Really appreciate that Jeppe!
comment in response to
post
Ah! Noice!
comment in response to
post
bang up job!
comment in response to
post
In action
comment in response to
post
If you're migrating without using sv migrate and use CI for code quality and haven't made your own CI for this, try it out, PRs more than welcome!!
bsky.app/profile/scot...
comment in response to
post
😂
comment in response to
post
Even for updating canvas?
comment in response to
post
Hi everyone 👋
comment in response to
post
You know what, after working out where the infinite loops come from, tracing up the render tree it was ok really
Didn’t use sv migrate, got a load of state to migrate still
comment in response to
post
Loving it!
Currently making a CI script so that PRs using effect badly or just Svelte 4 files it fails CI 😅
My team love me!!
comment in response to
post
And making sure the team STOP USING EFFECT WHEN INITIALISING PROPS
comment in response to
post
Three weeks in, three apps all reasonably sized
What’s taking the time?
We just gone added in vitest-browser-svelte for client side tests
And changed our testing strategy
Oh, and migrating from stores to Svelte 5 reactivity
And managing my team
And reviewing current sprint PRs
comment in response to
post
Absolutely not, there’s other options if you are not already locked into their ecosystem and decision makers are open to other options
comment in response to
post
The full changelog is available at github.com/vitest-dev/v...
comment in response to
post
Yeah, confuses it even more in my experience, even directly giving it the files in the chat
I managed to get the Windsurf one down to a smaller size, I’ve not tried it outside of that repo though, but have ~2k tests to be looking at converting so will see 😅
comment in response to
post
Yeah, windsurf has it pick up from the folder it’s in a think but cursor is that format
comment in response to
post
@dominikg.dev did bring this up yeah, I think we’re still debating exactly how though. Like either or, or specifically one route
comment in response to
post
Yeah, tried it even, worse results splitting it across many files to be honest
comment in response to
post
😅
comment in response to
post
Ohshit!
David, you the man tho! 😭
comment in response to
post
Meh! The only reason I did this was to make a cursor rules file that would cover all the scenarios 😂
comment in response to
post
What I'm leaning toward is minimal mocking (only DB/external services) while keeping form parsing real, plus shared validation logic between client/server. E2E tests catch any remaining integration gaps.