(no title)
danbulant | 3 years ago
Typescript is already supported when you set it up using the documented "npm create svelte@next".
It has cool routing, backend etc but even if you don't care about any of it, you get free hot reloads. And with the new version, you can create it as if it was your average svelte app, just avoiding + in file names and using +page.svelte as your main entry point.
For styles, if you care about styling a bit more than default styles (mvp.css or bulma/bootstrap/similar), I'd recommend using tailwind's better clone windicss, which has great svelte integration (including editor extensions for autocomplete and highlight), and writing styles is quicker than using normal css.
You can also use scss/sass/similar in style blocks, you only need to install node-sass and set "scss"/"sass" as the lang of the style block.
tekkk|3 years ago
Okay sure, they have had big breaking changes in-between major versions as well, but before SvelteKit hits v1.0 you're better off using something more stable. Later you can certainly choose to migrate as the core logic probably is not that complex. If you're using rich-text editing capabilities however, React is more supported.
ovao|3 years ago
That said, if you start working on a given pre-release and only upgrade to 1.0, the migration shouldn’t be too painful.
tobr|3 years ago
dceddia|3 years ago
cpfohl|3 years ago