Our little company was heartbroken by Vue 3 composition API and been learning, migrating, and started building new projects using Svelte 4.
I understand the needs why to add "opt-in" support for Runes (which from the blogs sounds like the way to go in the long run).
It was also mentioned that the current Svelte (Svelte 4 way) will be supported in Svelte 5 (but there's a high chance of being deprecated or not maintained -- see Vue Class Component being ditched https://github.com/vuejs/vue-class-component/issues/632 even after assurances from Vue team)
Describe the proposed solution
Is there a possibility or plan that we can use Svelte 4 and Svelte 5 syntaxes separately and without them being mixed in 1 svelte file?
For example in the Githubissues.
Githubissues is a development platform for aggregating issues.
Describe the problem
Our little company was heartbroken by Vue 3 composition API and been learning, migrating, and started building new projects using Svelte 4.
I understand the needs why to add "opt-in" support for Runes (which from the blogs sounds like the way to go in the long run).
It was also mentioned that the current Svelte (Svelte 4 way) will be supported in Svelte 5 (but there's a high chance of being deprecated or not maintained -- see Vue Class Component being ditched https://github.com/vuejs/vue-class-component/issues/632 even after assurances from Vue team)
Describe the proposed solution
Is there a possibility or plan that we can use Svelte 4 and Svelte 5 syntaxes separately and without them being mixed in 1 svelte file?
For example in the Githubissues.