chore(deps): add esbuild as explicit devDependency#5173
Merged
Conversation
powertools-for-aws-oss-automation
bot
added
size/XS
powertools-for-aws-oss-automation
bot
added
size/XS
|
svozza
approved these changes
Apr 7, 2026
Contributor
|
I disagree that this should be a root-level package. AWS CDK is not a root level package either and is instead used (and depended upon) in |
2 tasks
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
3 participants
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
Changes
Add
esbuildas an explicitdevDependencyin the rootpackage.json. After the Vitest upgrade moved to Vite 8, esbuild was dropped as a transitive dependency since Vite 8 switched from esbuild to Rolldown. This caused CDK'sNodejsFunctionto fall back to Docker-based bundling during e2e tests, resulting inexec format errorfailures on CI runners.Issue number: closes #5172
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.