moreover, the shipped version is TS 5.3, while we are already at the 5.8 version

It's a good new to at least been able to use TS5.

However, I still don't get why you are forcing us to use a specific version of TS.

The spfx build chain first transpiles TS to JS, and THEN webpack bundles the resulting js..

Why can't you simply let us use any TS version ?

does not works with the latest firefox stable
is it a standardized feature?

The main drawback of this approach is that bootstrapping a new project is not straightforward:

pnpm --package yo@latest --package @microsoft/generator-sharepoint@latest --package mem-fs dlx yo @microsoft/sharepoint@latest --skip-install --package-manager pnpm

My typical setup:
* install node latest LTS version
* install pnpm
* use .npmrc in every project to target the supported node version for the specific SPFX version

I used nvm some times ago, but I found easier to use pnpm env feature

700 mo de même oqp par le système

Les temps ont bien changé

Le chien dans the mask ?

does it support SSO too ?

Wonder what was the use cases of such devices

My main target is to build SharePoint framework extensions (learn.microsoft.com/en-us/sharep...)
The stack provides its own build chain, embedding a custom webpack build (which fix react to 17, typescript to V4 and a lot of other irratating limitations).
I heavily use react query ... V4 ;)

Tanstack deserves it

If only I could move my stack from react 17 to 18 :(

Running backend with javascript is the worst thing I've heard

What's the line that seems to starts from the center ?

Csr only

tu peux étayer les "2"
et oui, je sais bien que la cyber nécessite les autres compétences en amont (dev, réseau, ..., une bonne culture G info en général) avant tout