feat(cli): add typescript support by bundling processor with esbuild #2360
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.
Description
Adds support for typescript processors in run and run-fargate.
Some of the decisions that were explored and ended up being made:
aws:lambda
due to an issue with bundle sizes. Will be explored again later. As this is primarily for Playwright Typescript support, and Playwright does not run in Lambda, this is not urgent;esbuild-wasm
as it is cross-platform compatible. Regularesbuild
also works and installs the platform specific binary, but this is more future-proof for when we do provide Lambda support. This can easily be changed;global.artillery.hasTypescriptProcessor
. This can be changed a little bit later by refactoring some of the logic inrun
, but right now it felt unnecessary to tackle immediately.Pre-merge checklist