feat(es/typescript): Add esm build for fast ts strip

[magic-akari]

Related issue (if exists):

• Closes: Add ESM exports to @swc/wasm-typescript #9283

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8c8a0fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kdy1]

How will this work while publishing? I think this will add esm Wasm binary to the original package, right?
I think it may cause an issue for node.js team due to the size of the binary. Can we have another entry at

swc/.github/workflows/publish-npm-package.yml

Lines 587 to 596 in c1cd0b9

	settings:
	- crate: "binding_core_wasm"
	npm: "@swc\\/wasm"
	target: nodejs
	- crate: "binding_core_wasm"
	npm: "@swc\\/wasm-web"
	target: web
	- crate: "binding_typescript_wasm"
	npm: "@swc\\/wasm-typescript"
	target: nodejs

instead?

[codspeed-hq]

CodSpeed Performance Report

Merging #9286 will not alter performance

_{Comparing magic-akari:feat/ts-strip/esm (8c8a0fe) with main (76fe139)}

Summary

✅ 178 untouched benchmarks

[magic-akari]

How will this work while publishing? I think this will add esm Wasm binary to the original package, right? I think it may cause an issue for node.js team due to the size of the binary. Can we have another entry at

swc/.github/workflows/publish-npm-package.yml

Lines 587 to 596 in c1cd0b9

	settings:
	- crate: "binding_core_wasm"
	npm: "@swc\\/wasm"
	target: nodejs
	- crate: "binding_core_wasm"
	npm: "@swc\\/wasm-web"
	target: web
	- crate: "binding_typescript_wasm"
	npm: "@swc\\/wasm-typescript"
	target: nodejs

instead?

I agree.

[magic-akari]

I tweaked the CI logic.
This is the most troublesome because I don't know if it will work the first time.

[kdy1]

I'll try using nightly