Client modules using typescript should depend on the typescript module

[murdos]

Following a recent discussion on the addition of new modules adding typescript utilities, it demonstrates that we currently have an issue regarding typescript related modules.

Let's pick the optional-typescript as an example: it requires the typescript.
So if you have applied for example the vue-core module, you can't use it unless you also apply the typescript module which will generates conflicting npm configuration (e.g. setting up jest in addition to already setup vitest).

On the contrary the new modules, ts-loader and ts-pagination-domain only requires the init module, which is convenient for matching both use cases, but a bit wrong since code will not compile if you don't have already applied a module that'll setup typescript.

My suggestion is to rework the typescript module to make it use a modern setup (eslint, vitest), and have at least vue-core and react-core modules (angular could be nice too, but it has a very specific build tools so this might be a bit more complicated) depend on the typescript module.

@pascalgrimaud @qmonmert @DamnClin @renanfranca : WDYT?

Related: #3979

• Vue: Vue module now depends on typescript module #10840
• React: feat: react module now depends on typescript module #10914
• Angular ?
• Svelte ?

[renanfranca]

I agree with this 💯 👌. It will help new frontend devs 😁👍