Hacker News new | ask | show | jobs
by IshKebab 1612 days ago
Damn I was hoping Svelte had proper Typescript support given that they claim that Svelte officially supports TypeScript. Is it just like Vue - it "supports" it, but there's still important stuff that's not type checked at compile time?
2 comments
marcus_cemes 1612 days ago
Well, good news for you, it does! Very well, in fact. Svelte itself is written in TypeScript.
link
IshKebab 1611 days ago
So is he wrong about not being able to type check that then?
link
marcus_cemes 1611 days ago
Well, yes, to my understanding. If you add lang="ts" to the script block, you can write normal TypeScript code for the component logic, and it will also check props that you are passing to child components in the template. It's like renaming the file from ".jsx" to ".tsx". It might not be perfect, but I haven't encountered any problems with it so far.
link
The_rationalist 1612 days ago
Vue 3 is written in typescript and does type check props at both compile time and runtime.
link
IshKebab 1611 days ago
Not very nicely: https://v3.vuejs.org/guide/typescript-support.html#annotatin...

Does it type check templates yet?

link
The_rationalist 1611 days ago
Nobody should still use the awful legacy vue component syntax, it is trivial and much cleaner to migrate to script setup components, which do provide properly type checked props easily https://v3.vuejs.org/api/sfc-script-setup.html#defineprops-a... https://v3.vuejs.org/api/sfc-script-setup.html#typescript-on... (although vue class component is still the best API of all VDOMs, it's unfortunate its development has stalled)

Webstorm now properly supports template type checking too https://blog.jetbrains.com/webstorm/2021/11/webstorm-2021-3/...

link
IshKebab 1611 days ago
Nobody should use the thing that the documentation tells you to use...

Vue 3 looks a lot better than Vue 2 but honestly it's just playing catch up to React. I don't know why you'd choose it.

link
marcus_cemes 1611 days ago
It might interest you that Wikipeida chose Vue to modernise its frontend in the future [1]. Different frameworks offer different benefits and different downsides.

React is not the end-all, nor will it ever be, as long as there are interesting new projects coming out, and neither is Vue or Svelte. My website uses React, but personally I would rather use Vue or Svelte in the future.

[1]: https://phabricator.wikimedia.org/T241180

link
IshKebab 1610 days ago
Yeah we chose Vue at work too, but it was only because we didn't have enough experience of either.

> Wikipeida chose Vue

Yeah their reasons look very much like dubious attempts to justify the choice someone has already made.

1. You can use it without a build step.

Sure, but only if you're not using Typescript, which would be mad. A build step is a mild inconvenience. Not something that should cause you to choose a worse solution (though they do also use PHP so they're probably used to bad tech).

2. Vue.js may enable us to rely on fewer libraries as dependencies.

Ha! When I added Vue and its required CLI stuff to our package.json it pulled in around 1000 dependencies. React has like 4.

3. The official Vue libraries are evolving in a stable and predictable fashion.

You can still use React classes if you want to. They're not deprecated. It's unlikely they ever will be.

4. Vue.js development is not led by a single corporation whose goals may diverge from those of the WMF.

I mean... come on.

link