-
Notifications
You must be signed in to change notification settings - Fork 580
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
Typescript 3.7.x breaking @aws-sdk/types ... again #2474
Comments
I am also experiencing this issue, would be good if this gets resolved quickly |
I'm experiencing the same issue with Typescript
|
Same here with Typescript |
I'm also seeing this with TS |
I figured out the issue, which seems to be twofold:
Should be:
I verified this by running #2 is simple to fix and I'm trying to debug |
v3.10.0 has the folder published, but starting at v3.12.0 it is no longer there. It was between those releases that |
The PR which moved running downlevel-dts in prepublishOnly step #2218 In the PR it was verified that:
|
Noticed the following error from our release log:
|
The issue appear to be with our release script, where |
The types are now there, however, the second issue I listed still exists: #2474 (comment) typesVersions is pointing to the wrong place:
Should be:
I just opened a PR for this fix: #2579 |
Thank you @TreTuna for the PR! The change was required to be done in codegen as well as all packages. Your commit was picked and subsequent PRs were posted at: |
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. |
Describe the bug
Same as #1919 - twas fixed in aws-sdk 3.4.0, but seems to be back since 3.10.0.
@aws-sdk/types
declaresUserAgentPair
.Pairs are not supported in Typescript 3.7.x
https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/#labeled-tuple-elements.
Users running typescript < 4.0.0 cannot correctly get types.
Your environment
SDK version number
3.10.0+
Is the issue in the browser/Node.js/ReactNative?
All
Details of the browser/Node.js/ReactNative version
node v10.24.1
tsc 3.7.5
Steps to reproduce
Observed behavior
The following error is thrown for the code example give below:
lab_63.js
package.json
tsconfig.json
Expected behavior
No error is thrown when compiling client code with TypeScript version 3.7.x
The text was updated successfully, but these errors were encountered: