fix(ci): replace top-level await with async IIFE in CI runner#61
Merged
Conversation
tsx defaults to CJS output which does not support top-level await. Wrapping the async logic in an IIFE avoids the need for ESM output and works with any tsx version without extra flags. Also reverts the --esm flag from the workflow (not a valid tsx flag).
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.
Fix
Second attempt at fixing the
deploy-sapworkflow failure.Root cause:
tsxdefaults to CJS output, which does not support top-levelawait. The previous fix attempted--esmas a tsx flag, but that is actually a Node.js flag — tsx rejected it withbad option: --esm.Fix: Wrap the async logic in a
void (async () => { ... })()IIFE. This works regardless of output format and requires no flags.