-
Notifications
You must be signed in to change notification settings - Fork 597
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
@aws-sdk/node-config-provider should be a full dependency of @aws-sdk/config-resolver #4481
Comments
|
@RanVaknin Is there a way around this in the meantime? |
@spbarber pnpm supports patching package definitions via the
Which essentially tells pnpm to treat |
|
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. |
Checkboxes for prior research
Describe the bug
@aws-sdk/config-resolver
lists@aws-sdk/node-config-provider
as a devDependency, but depends on it for types, so it should be a full dependency.This is the same as #4191 but with full reproduction steps.
SDK version number
@aws-sdk/config-resolver@3.272.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v16.17.1
Reproduction Steps
tsconfig.json:
index.ts:
Run
pnpm tsc
.Observed Behavior
Expected Behavior
Compiles successfully.
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: