[SHIP-1981]: Use commonjs module for ts-node compatibility#6
Merged
adriantaut merged 1 commit intomainfrom Jan 22, 2026
Merged
Conversation
- Change tsconfig to use commonjs (like zarpay/core) - Remove .js extensions from imports - No build step needed before cdk commands
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
1 participant
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.
Summary
Fix CDK failing with
Cannot find module '../lib/fizzy-stack.js'error.Root cause: Fizzy used
NodeNextmodule with.jsextensions in imports, which requires compilation before running. Core usescommonjswhich ts-node handles natively.Changes
commonjs(matching zarpay/core).jsextensions from all importsyarn buildstep needed before CDK commandsTest plan
yarn cdk synth --context imageVersion=testruns without module errors🤖 Generated with Claude Code