Ivan Hofer

@samuelstros @inlangHQ I am looking forward to the next exciting months 🚀

lovely message. 22 months later, welcome @ivanhofer_ to @inlangHQ :party:

@trueadm @raw Right, but could be a bit intransparent for beginners 😅

@ivanhofer_ @raw You don't need a helper though, just do {x + ''}

I've been doing some digging into how various frameworks handle rendering of values different types of value to the UI. Take: <div>{value}</div> What should happen if `value` is null, undefined, a boolean, function, object, array or function? Should it render an empty string?

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 → marketplace.visualstudio.com/items?itemName…

@itschrisjayden @BertBengtson The new helper type was introduced a few months ago. You are using the old syntax 😊

@BertBengtson I think I was doing it the wrong way 🤦🏻

How come no one told me about this!? This fixes like all my problems with Svelte typescript 😭

@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 🌍

@ivanhofer_ Thanks @ivanhofer_ ! Follow up question - Once inlang is released as a stable version and gets good traction from community, will typesafe-i18n be deprecated in favor of inlang?

@ivanhofer_ - you being the author of both the i18n libraries, when would you recommend to use typesafe-i18n over inlang-sdk and vice versa in #SvelteKit?

@aakashgoplani Migrating from `typesafe-i18n` to the inlang SDK will probably just be deleting some code and running an automated script 😊

@aakashgoplani Or just wait a few months until the inlang development catches up with more features 😊

@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 🚀

@celikovic @derlukasg @figma Indeed! Pinging @samuelstroschei, who once mentioned that he has plans to support figma with @inlangHQ.

@derlukasg @figma This might be interesting use case for your tool, @ivanhofer_

Anybody already working on a @figma variables plugin for translations? I want to create a full prototype flow in one language > run the plugin > go through all strings > create translation variables for them > apply them (applying the same var to recurring strings) 👀

@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

For those of you who use Svelte, what features/changes would you love to see in Svelte 5?

Come join us for our 1 year anniversary @sveltejs meetup in #Vienna. Wanna give a talk? Just send us a DM. lu.ma/2023-06-svienna @SvelteSociety

@puruvjdev Thanks! The video shows an early alpha version and we plan to release a more stable version in a few weeks 😊

HOLY SHIT!!! Hats off @ivanhofer_ youtube.com/watch?v=Y6IbPf…

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😅

@thomasglopes Sounds great! Looking forward to see it happen 🚀

@alexannajjar Great to hear!

.@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 inlang.com