Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(signature-v4-multi-region): make conditional require call in node.js only #5203

Merged
merged 1 commit into from
Sep 13, 2023

Conversation

kuhe
Copy link
Contributor

@kuhe kuhe commented Sep 12, 2023

related to #5135
mentioned in #4797
fixes #4464
related to #2822
partially addresses #4126
fixes #4373

  • inverts the dependency between signature-v4-crt and signature-v4-multi-region. crt now depends on multi-region, and multi-region does not depend on crt, even optionally.
  • why? To avoid the conditional runtime require being analyzed as a static import by bundlers. Now, if you install signature-v4-crt, it will inject itself into a container that is used by signature-v4-multi-region.

revision 1:

@kuhe kuhe requested a review from a team as a code owner September 12, 2023 22:08
@kuhe kuhe force-pushed the fix/crt branch 2 times, most recently from f04a3ad to a3b1fa9 Compare September 12, 2023 22:16
Copy link
Contributor

@AllanZhengYP AllanZhengYP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice to have this fixed! Thank you @kuhe

@kuhe kuhe changed the title fix(signature-v4-multi-region): avoid require call on optional dependency fix(signature-v4-multi-region): make conditional require call in node.js only Sep 13, 2023
@kuhe kuhe merged commit 0a68c97 into aws:main Sep 13, 2023
@kuhe kuhe deleted the fix/crt branch September 13, 2023 17:34
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants