build: add ts support in core modules

[marco-ippolito]

Let's try again.
This PR allows Node.js source code to be written in TS.
This is semver major because the build now always requires rust to be installed.
This adds swc as a rust crate dependency and it's only use during build time.
Technically we could replace amaro wasm with this for type stripping but it's not the goal of this PR and in needs other considerations.
I moved an internal from .js and .ts to showcase
Also added a flag so that the transpiled code can be writte on the fs for debugging.
A lot of the addition are vendored crates sorry for the massive PR
I used AI to help me out with things I dont know (rust) so please review carefully
I had to bump the rustc from 1.82 to 1.85, obviously this cannot land if we dont update that on the CI machines

[nodejs-github-bot]

Review requested:

• @nodejs/build
• @nodejs/gyp
• @nodejs/security-wg
• @nodejs/tsc

[anonrig]

@marco-ippolito do you know what steps are needed to run and expose Rust code just like C++?

[marco-ippolito]

@marco-ippolito do you know what steps are needed to run and expose Rust code just like C++?

its already done in this PR, see d9ee95f

basically add the crate in the deps/crates cargo.toml, create a header file if doesnt come with the crate and add it to the node gyp

[ljharb]

Will this type strip at runtime? Or will it do it at build time?

[marco-ippolito]

Will this type strip at runtime? Or will it do it at build time?

Build time

[ljharb]

How does this interact with the --node-builtin-modules-path flag? will it still type strip at runtime in that case?

[aduh95]

Not that this will have been deleted by

node/Makefile

Line 1220 in 3725bd2

$(RM) -r $(TARNAME)/deps/crates

[marco-ippolito]

Yeah I still figure out the shared build with nix. I have never touched this part so I dont really know how it works

[marco-ippolito]

How does this interact with the --node-builtin-modules-path flag? will it still type strip at runtime in that case?

Yes, I tested it, it works fine. it plugs in the js2c module

[mcollina]

I'm relatively concerned about adding 1 million and 300 hundred thousand lines of code, even if they are just dependencies.

Is there a solution that does not require this much?

[marco-ippolito]

I dont think so since we are vendoring dependencies. I think the only solution is to have an automation generate them but its kinda impossible to review anyways. (The temporal PR from @legendecas had the same problem)

[legendecas]

I think the question should be is it necessary to have every swc dependencies to be included?

I listed the newly added dependencies, and the followings are the biggest deps that I doubt if they are required:

9.6M	deps/crates/vendor/tracing          => Diagnostic purpose
5.1M	deps/crates/vendor/libc             => Indirect dep of crates `cpufeatures` and `num_cpus`
2.8M	deps/crates/vendor/regex-automata   => Regex engine
1.6M	deps/crates/vendor/bitvec           => Indirect dep of swc_sourcemap
1.6M	deps/crates/vendor/zerocopy         => Indirect dep of hashbrown
1.3M	deps/crates/vendor/zerocopy-derive  => Indirect dep of hashbrown
1.0M	deps/crates/vendor/idna             => Indirect dep of crate `url`

Additionally, crates like wasm-bindgen are not technically needed for the PR purpose.

I think technically many of these deps can be stripped down.

[marco-ippolito]

Can I just like delete them and see if it builds?