We're happy to announce the launch of our VSCode Extension (beta).
It helps developers do daily translation-tasks much more efficiently and comes together with a hand full of great features. 👨💻⚡️
Download it here → https://t.co/n4lorvQ38o
@aakashgoplani Could be an option, but we are still quite some time away from that point. The inlang SDK currently focuses on SvelteKit (and soon Next.js 👀) while `typesafe-i18n` works on everything that runs JavaScript 🌍
@aakashgoplani Eventually the @inlangHQ SDK will improve every aspect of `typesafe-i18n`, but still needs some time until that happens. Beeing able to build a specific solution for a metaframework opens up interesting possibilities, we want to explore in the future 🚀
@trueadm@SvelteSociety - SSR-only components, that don't ship JS code to client, they don't need to hydrate and just render what the server did output (not sure if this belongs to Svelte or SvelteKit)
- more robust VS Code extension (in larger projects I have to restart it multiple times per day)
@trueadm@SvelteSociety - optimizing compiler output further
- better TypeScript support (you can type almost everything already, but it is experimantal and a bit verbose)
- function to parse a .svelte file to an AST and to serialize the AST back to a string representation
Thinking of doing a website for @ivanhofer_'s SvelteKit Typescript Showcase. I constantly refer to it, and would be really nice to have it with search, side-by-side code panels, etc.
I need to find the time to do it though😅
.@ivanhofer_ introduced inlang, a Vite-based internationalization (i18n) solution that works in SvelteKit! i18n is a hard problem (evidenced by the 150+ message on the open SvelteKit issues), it's great to see a solution being worked on! #SvelteSummit
https://t.co/TJKC75ogqp