Remove top-level awaits to enable bytecode compilation #4868
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.
Currently this PR is not enough to enable bytecode compiliation
Expected CommonJS module to have a function wrapper. This us often caused by the use ofimport.meta.urlor other ESM only code. This needs more investigationPreparation for enabling bytecode compilation (faster startup times).
Related to #4843 and sst/opentui#356
await cli.parse()toPromise.resolve(cli.parse()).catch().finally()patternawaitfromLog.init()call (fire-and-forget)Once opentui PR lands and Bun types are updated, bytecode can be enabled in
build.tswithbytecode: true.