Frontend

nothing is more disappointing than a library providing only react support.

"nobody has time to make versions for each framework!"

not what we are asking and not what you should do even if you're able to. Just make a vanilla JS version and a react version.

This ends up being better for your library long term

Treat React Hooks for what it is – a separate programming language.

Hooks happen to use JavaScript-y syntax and package mechanisms, but they ignore all the usual conventions around references and closures due to the implied re-rendering loop and are thus incompatible with the rest of the JavaScript ecosystem.

I like how as of Svelte 5, all rune-based reactivity outside of components must be contained within `.svelte.js` / `.svelte.ts` files. This lets you explicitly mark that something is written for a Svelte-based runtime while keeping compatibility with JavaScript import tooling.

Would love to see this become a trend.

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

I like how as of Svelte 5, all rune-based reactivity outside of components must be contained within `.svelte.js` / `.svelte.ts` files. This lets you explicitly mark that something is written for a Svelte-based runtime while keeping compatibility with JavaScript import tooling.

Would love to see this become a trend.

https://svelte.dev/docs/svelte/svelte-js-files