build: migrate to esm, vitest and oxlint - #921
Merged
Merged
Conversation
commit: |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please describe the changes this PR makes and why it should be merged: Migrates the template to a single native ESM TypeScript 7 build, replaces Jest and ESLint execution with Vitest/Oxc and the approved Oxlint profile, updates Nest development dependencies to 12.0.1 with Nest 10/11/12 peer ranges, adds explicit package exports/files/engines, converts relative runtime specifiers to .js, and updates CI for the supported Node matrix. No tests or package-smoke tooling were added. Status and versioning classification: Build and package-contract migration. This is breaking for Node versions below 20.19, CommonJS-era tooling that cannot load ESM, and Nest 8/9 consumers. Verification: npm ci; npm run lint; npm run typecheck; npm run build; npm run test:ci (zero test files, exit 0); npm pack --dry-run --json; package metadata and workflow syntax checks. Typings were rebuilt and require no public API additions or removals.