Repository navigation
chore(examples): move the TypeScript examples to tsx and TypeScript 6 - #419
Merged
jsteinich merged 2 commits intoSep 12, 2026
Merged
Conversation
so0k
approved these changes
Sep 11, 2026
The init template moved to tsx in open-constructs#396 because ts-node cannot be used with TypeScript 6: it merges a bundled @tsconfig/nodeXX default that supplies a deprecated `moduleResolution: node10`, which the compiler rejects. The examples still ran `npx ts-node main.ts`, so they demonstrated a setup the CLI no longer produces, and copying their config into a generated project would reproduce that failure. The documentation example was already on tsx; its pin is brought in line with the rest. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Brings the examples in line with the packages (open-constructs#406) and the init template (open-constructs#396), which now generates projects on TypeScript 6. Only possible now that the examples run on tsx: TypeScript 6 with ts-node fails synth with TS5107. Two config changes are needed, the same ones the template took: - `types: ["node", "jest"]`, because the tsconfigs include `__tests__` and the jest globals otherwise stop resolving. - `isolatedModules` in azure-service-bus-queue-trigger, the one example with a ts-jest preset, which cannot emit under TypeScript 6 in language-service mode. No example sets `baseUrl`, so none of that cleanup applies here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jsteinich
force-pushed
the
claude/examples-tsx-typescript-6
branch
from
September 12, 2026 02:05
86d7436 to
582fdd4
Compare
This was referenced Sep 12, 2026
Contributor
|
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related issue
Alignment follow-up to #396 (init template → tsx + TypeScript 6) and #406 (packages → TypeScript 6). The examples were the last part of the repo still on ts-node and TypeScript 5.
Description
Two commits, in the order they have to happen:
1.
chore(examples): run the TypeScript examples with tsx(669eae2)21 of the 22 TypeScript examples ran
npx ts-node main.ts. ts-node cannot be used with TypeScript 6 — it merges a bundled@tsconfig/nodeXXdefault supplying a deprecatedmoduleResolution: node10, which the compiler rejects — so the examples demonstrated a setup the CLI no longer produces, and copying their config into a generated project reproduces that failure. Thedocumentationexample was already on tsx; its pin is brought in line.2.
chore(examples): move the TypeScript examples to TypeScript 6(86d7436)typescriptgoes from^5.0.0to~6.0.0, plus the same two config changes the template needed:types: ["node", "jest"]— the tsconfigsinclude__tests__, and TypeScript 6 otherwise stops resolving the jest globals (Cannot find name 'describe').isolatedModulesinazure-service-bus-queue-trigger, the only example with a ts-jest preset, which cannot emit under TypeScript 6 in language-service mode.No example sets
baseUrl, so none of that cleanup applies here.The commits cannot be reordered or split into separate PRs: TypeScript 6 with ts-node is exactly the broken combination, and CI exercises both halves —
tools/build-example.mjsrunsbuild(→tsc, which hits thedescribeerror) and thensynth(→ the app command, which hits TS5107).Verification
Beyond type-checking, one example was taken end to end locally on TypeScript 6.0.3:
The rest are covered by the Examples Integration matrix.
Checklist
The diff is 65 files but highly repetitive — three small edits repeated across 22 examples.
🤖 Generated with Claude Code