Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- node-internal

Epic Link:
Node V5
Quarter:
- FY23Q4
Story Points:
3
Compass/DevTools Changes:
Not Needed
Confidence Status:
None

Documentation Changes:
Not Needed

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Link:
None
Goal Name(s):
None

We should investigate how optional vs peer dependencies are handled in the different package managers (npm, yarn, deno).

We need to outline the pros/cons of each way of specifying the dependency alongside a plug-in approach (more like we do with our own add-on packages, such as kerberos), and pick a consistent way to move forward for our credential auth.

is depended on by

NODE-4537 Support the Azure VM-assigned Managed Identity for Automatic KMS Credentials

Closed

is related to

NODE-4898 Make @aws-sdk/credential-providers an optional peerDependency

Closed

NODE-4977 Import snappy dependency lazily when feature is used

Closed

NODE-4830 refactor aws import to import aws on demand

Closed

related to

NODE-4736 Move AWS optional dependency to peerDependencies

Closed

split from

NODE-3562 Codify optional dependency version support

Closed

links to

Spike investigation notes

(1 split from, 1 links to)

Assignee:: Neal Beeken
Reporter:: Daria Pardue
Reviewers:: Daria Pardue
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Nov 18 2022 09:02:56 PM UTC
Updated:: Mar 16 2023 11:02:02 PM UTC
Resolved:: Jan 26 2023 10:27:25 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates