Regarding Rune Syntax #2802
-
I used a translation tool, so please let me know if there are any contextual issues. I'll provide more specific details. Hello, I have attempted to implement internationalization using Svelte 5. Currently, since the Rune syntax is in preview, Google searches often bring up pre-Svelte 4 syntax, which can conflict with Rune syntax. As a result, I always include the following in my //svelte.config.js
compilerOptions: {
runes: true
}, However, Thank you for reading my discussion. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
ping @opral/inlang-paraglide-js |
Beta Was this translation helpful? Give feedback.
-
Rune syntax is something we do want to support, given that it will be the new default in Svelte 5 and onwards! We so far waited to implement it until Svelte 5 finalized it's syntax, which seems to be the case now that it has reached Release-Candidate status. I created this issue to track progress on our implementation |
Beta Was this translation helpful? Give feedback.
-
Any updates on svelte 5? |
Beta Was this translation helpful? Give feedback.
Rune syntax is something we do want to support, given that it will be the new default in Svelte 5 and onwards!
We so far waited to implement it until Svelte 5 finalized it's syntax, which seems to be the case now that it has reached Release-Candidate status.
I created this issue to track progress on our implementation