meta: add support for TypeScript plugins

[aduh95]

• Adds support for TS sources in package.
• Edits tsconfig.json so running yarn tsc generates the .d.ts files corresponding to the .ts.
• Removes support for CJS sources in packages, which we no longer use since Uppy 3.0.
• Upgrades TypeScript so we can use allowImportingTsExtensions
• Adds yarn build:ts to check for TS errors.
• Adds a script that migrate a JS package to TS

To migrate a package, run node private/js2ts/index.mjs @uppy/utils. This will rename all the files from .jsx to .tsx and .js to .ts, and change the import statements.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@babel/plugin-transform-typescript	7.22.15	None	+0	130 kB	nicolo-ribaudo
parcel	2.10.0...2.9.3, 2.8.3...2.9.3	None	+105/-150	499 MB	devongovett
tsd	0.22.0...0.28.1	None	+1/-1	53.8 MB	sindresorhus

🚮 Removed packages: [email protected], [email protected]

[arturi]

@Murderlon ready for your review / test, please 👌

[Murderlon]

I was briefly able to testing typing a package, @uppy/utils, to see what it is like. Overall it seems to work well, so job well done! 👏

Some observations:

• The private/js2ts/index.mjs script only works on Node.js 20.1.0. Ideally this should be able to run on LTS as well as I reckon most members and contributors use that too.
• Types in tests are currently a problem. Because they are excluded in tsconfig, the settings don't apply there, resulting in errors such as An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled, which is a setting we have in fact set. One solution might be to simply not convert tests to TypeScript, but that means importing from the compiled version and making tests dependent on a build step. Another options could be to have a dev tsconfig, which does include tests and it only used locally (using a different command in package.json which explicitly passes the other tsconfig).
• We probably want to have @yarnpkg/plugin-typescript.

I wanted to investigate a bit more and contribute some of these changes but other things ended up taking more time this week. Next week I'm not working. Excusez-moi.

[aduh95]

• The private/js2ts/index.mjs script only works on Node.js 20.1.0. Ideally this should be able to run on LTS as well as I reckon most members and contributors use that too.

AFAICT it works with Node.js 18.17+, which is LTS. Maybe you are using an older LTS version?

[aduh95]

My editor resolves to the nearest tsconfig. When working with a package such as @uppy/utils this means that tsconfig is resolved and not the root one, which is where we added one for tests. Hence my LSP doesn't work correctly for tests.

Shouldn't you fix that / use one that works correctly? Or maybe disable it for test files if you can't find a quick workaround.

At the very least I would expect that the same tsconfig settings are applied to tests (either all of them or extend'd)

It seems to me we may want different settings (e.g. we do not want to transpile them to lib/). Extending is a good idea though.

[nickrttn]

Furthermore we should tests whether we even need a different tsconfig for tests. In unified we have 300 repositories with TypeScript and none of them separate tests into a different config (example).

Typically this is only required if you want to emit JavaScript files via tsc. Usually the tsconfig.json is picked up by language servers automatically so you want that to work for all files, then a tsconfig.build.json or something like that that excludes test files. That's how I set it up here: https://github.com/motifland/markprompt-js/tree/main/packages/react

[Murderlon]

Typically this is only required if you want to emit JavaScript files via tsc. Usually the tsconfig.json is picked up by language servers automatically so you want that to work for all files, then a tsconfig.build.json or something like that that excludes test files. That's how I set it up here: https://github.com/motifland/markprompt-js/tree/main/packages/react

Yes, this makes more sense! Currently we try to use both the root tsconfig and the local package tsconfig at the same time which isn't a good idea and won't work in all editors. With this suggestion we always resolve to locally scoped tsconfig, which has everything we need.

[Murderlon]

Added my review in the other PR: #4699 (review)