fix(logger): fix esbuild ESM bundler error #4678
Merged
Conversation
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
…)" This reverts commit 5199d3e.
boring-cyborg
bot
added
commons
pull-request-size
bot
added
the
size/XXL
|
svozza
changed the title
|
E2E tests have passed: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/18748386048 |
sdangol
approved these changes
Oct 23, 2025
svozza
added
do-not-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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
Tte InvokeStore dependency added in #4658, is packaged as a CJS module and because it uses a Node API (node:async_hooks), this causes problems for ESBuild when it tries to bundle to ESM.
We must revert #4658 and #4663 as they both use
InvokeStore.Changes
Issue number: closes #4677
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.