Uh oh!
There was an error while loading. Please reload this page.
ref(build): Replace ts-node with tsx for build and CI scripts - #22186
Merged
Conversation
logaretmforce-pushed
the
awad/migrate-ts-node-to-tsx
branch
from
July 10, 2026 18:37
8f29231 to
34a136bComparelogaretm
changed the base branch from
develop
to
awad/js-1293-drop-typescript-38-supportJuly 10, 2026 18:38
This was referenced Jul 10, 2026
logaretmforce-pushed
the
awad/migrate-ts-node-to-tsx
branch
from
July 10, 2026 18:49
34a136b to
9549b5cComparelogaretmforce-pushed
the
awad/migrate-ts-node-to-tsx
branch
2 times, most recently
from
July 10, 2026 19:00
f0bcefb to
96ab381Comparelogaretm
changed the base branch from
awad/js-1293-drop-typescript-38-support
to
developJuly 10, 2026 19:00
Contributor
size-limit report 📦
|
Swap the ts-node script runner for tsx across all build/CI/e2e scripts and the node integration-test runners (node --import tsx). tsx uses esbuild so it runs on any TypeScript version, which unblocks upgrading the compiler. No behavior change on the current TypeScript.
logaretmforce-pushed
the
awad/migrate-ts-node-to-tsx
branch
from
July 11, 2026 00:56
96ab381 to
df9681dComparelogaretm
marked this pull request as ready for review
July 11, 2026 02:30
andreiborza
approved these changes
Jul 13, 2026
Uh oh!
There was an error while loading. Please reload this page.
logaretm added a commit
that referenced
this pull request
Jul 13, 2026
…lder (#22190) Replaces `@nuxt/module-builder` with a plain rollup + tsc setup for the `build/module` output. Rollup bundles the module entry and emits the runtime files one-to-one (preserveModules), tsc emits the declarations, and a small script writes `module.cjs`, `module.json` and `types.d.ts`. The point is to drop a build tool that consumes the TypeScript compiler API, so the package no longer pins us to a specific TS compiler, also streamlines nuxt SDK build step for future changes like rolldown. We still have E2E tests ensuring the module output is consumable by Nuxt apps, so that's not something I would worry about drifting in the future. Stacked on #22186.
49 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Swap the ts-node script runner for tsx across all build/CI/e2e scripts and the node integration-test runners (node --import tsx).
tsx uses esbuild so it runs on any TypeScript version, which unblocks upgrading the compiler. This is needed for TypeScript 7.0 upgrade and doesn't change much in our case.
Some tests required some changes because it relied on ts-node inlining
requirecalls without hoisting which esbuild in tsx is doing (matches ESM semantics), causing instrumentations to "miss". I adjusted the tests to use our instrumentation wrappers so that they behave like a real ESM environment.Added bonus is it has less dependencies, which our lock file now reflects.