Then I listen to click events on the container, and if e.target.matches(data-ref) I process it accordingly.
Is there a better way?
I'm replicating what ChatGPT does.
Then I listen to click events on the container, and if e.target.matches(data-ref) I process it accordingly.
Is there a better way?
I'm replicating what ChatGPT does.
A static asset took ~10ms, while an SSR'ed page took ~25ms.
A static asset took ~10ms, while an SSR'ed page took ~25ms.
Re ssr, fwiw (maybe not that much!), I asked ai, and it had this to say.
chatgpt.com/s/t_69175cb1...
Re ssr, fwiw (maybe not that much!), I asked ai, and it had this to say.
chatgpt.com/s/t_69175cb1...
@caddy.bsky.social (@vite.dev)
Easy as adding `domain()` to `plugins: [...]`. I work on tons of Svelte apps simultaneously, so this is a life saver.
npmjs.com/package/vite-plugin-domain
@caddy.bsky.social (@vite.dev)
Easy as adding `domain()` to `plugins: [...]`. I work on tons of Svelte apps simultaneously, so this is a life saver.
npmjs.com/package/vite-plugin-domain
(this is a follow upon my previous post bsky.app/profile/nuqa...)
* 1/5th and not 1/6.7th since there are a few more features to add to svelte version
(this is a follow upon my previous post bsky.app/profile/nuqa...)
* 1/5th and not 1/6.7th since there are a few more features to add to svelte version
> Data will never be preloaded if the user has chosen reduced data usage, meaning navigator.connection.saveData is true.
This makes sense, but not for mousedown/touchstart, as that will virtually always result in a click (right?).
So this simply slows down svkit sites.
> Data will never be preloaded if the user has chosen reduced data usage, meaning navigator.connection.saveData is true.
This makes sense, but not for mousedown/touchstart, as that will virtually always result in a click (right?).
So this simply slows down svkit sites.
npmjs.com/package/vite-plugin-domain
npmjs.com/package/vite-plugin-domain
Perhaps a bit of an extreme take :), but I do try to ‹adopt a “zero tolerance” philosophy›
Perhaps a bit of an extreme take :), but I do try to ‹adopt a “zero tolerance” philosophy›
@svelte.dev
@svelte.dev
Of course playwright adds complexity, but it's not a core part of my app, so I won't bump into it at every turn.
Of course playwright adds complexity, but it's not a core part of my app, so I won't bump into it at every turn.