Skip to content

Conversation

@tmm1
Copy link
Contributor

@tmm1 tmm1 commented Jan 22, 2025

This makes the ./build generated js code compatible with bun

Using bun instead of node results in faster compiles:

$ npm run watch
Finished compilation with 0 errors after 49305 ms
$ bun run -b watch
Finished compilation with 0 errors after 37214 ms

cc @jrieken @deepak1556

@tmm1 tmm1 changed the title build: switch build/tsconfig to module: nodenext build: switch build/tsconfig.json to module: nodenext Jan 22, 2025
@deepak1556 deepak1556 assigned joaomoreno and unassigned deepak1556 Jan 22, 2025
@joaomoreno
Copy link
Member

This is great, thanks @tmm1!

@vs-code-engineering vs-code-engineering bot added this to the January 2025 milestone Jan 22, 2025
@joaomoreno
Copy link
Member

joaomoreno commented Jan 22, 2025

Looking forward to the leak fix in a future TypeScript version: microsoft/TypeScript#58137

We'll also reach out to the TypeScript team and nudge them.

@bpasero bpasero requested a review from mjbvz January 22, 2025 11:24
Copy link
Member

@bpasero bpasero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes LGTM but I would love @mjbvz input too, given he is working on changing the module resolution for our sources in #236640

@bpasero bpasero merged commit e76c50f into microsoft:main Jan 22, 2025
7 checks passed
legomushroom pushed a commit that referenced this pull request Jan 22, 2025
* build/tsconfig: switch to module: nodenext for bun compat

* build: rewrite imports for nodenext compat

* build: re-generate
@Jarred-Sumner
Copy link

amazing

@jakebailey
Copy link
Member

Looking forward to the leak fix in a future TypeScript version: microsoft/TypeScript#58137

We'll also reach out to the TypeScript team and nudge them.

Are you specifically talking about a bun-related leak fix? I'm not sure that's specifically a bug in TS, given it does not affect other runtimes, and the proposed fix on that issue is not one that I personally think is one we should accept.

@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Mar 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants