4 ms·
You'll still be writing Javascript/Typescript with Svelte. What the article means by "Svelte 5 is not Javascript" is that all of your code outside things like S
by prophesi 2y ago
You'll still be writing Javascript/Typescript with Svelte. What the article means by "Svelte 5 is not Javascript" is that all of your code outside things like Stores will be compiled in a manner that makes it harder to debug, since it's not normal Javascript but a Svelte-compiled JS that won't make sense in the debugger.
I would opt for better debugger tooling specifically for Svelte than strip away the abstractions. Its the lack of a runtime managing a virtual DOM that makes it unique and performant, and frameworks like React also essentially have their own compilation step that obfuscates code. Source maps won't help much by itself; the React debugger is where you have a better view on your components and how things are wired up.
- barnabee 2y agoDebugging seems fine to me, theres even the {@debug …} tag. TypeScript is a better scripting language than JavaScript, Svelte is a better language/model/platform than HTML+TypeScript. React may be your cup of tea but I’d rather write Svelte templates every day! Not to mention per-component styles. Sure, a component inspector devtool would be neat, though. Nobody’s going to complain about better tooling :)
- deleted 2y ago[deleted]