"Property 'assetParameters' implicitly has type 'any'" error

[NGL321]

Typescript 3.6 had a bug where the noImplicitAny check would incorrectly be performed on private ambient private getters (such as assetParameters()).

This was tracked by our jsii issue #994, and resolved in Typescript PR #33896.

This issue no longer exists in Typescript >3.7.

However, for users using both Typescript <3.7 who have noImplicitAny: true in their tsconfig.json file (set to true in CDK 1.19.0), npm run build will result in the error:

node_modules/@aws-cdk/core/lib/stack.d.ts:425:17 - error TS7033: Property 'assetParameters' implicitly has type 'any', because its get accessor lacks a return type annotation.

425     private get assetParameters();
                    ~~~~~~~~~~~~~~~

This can be resolved by updating the typescript dependency to >=3.7 OR through either of the following workarounds in the tsconfig.json file:

noImplicitAny: true,  =>  noImplicitAny: false,

OR

+ skipLibCheck: true,

[bo67192]

I don't have much typescript experience, would it be reasonable to add a dependency to the core module for typescript ^3.7?

That way at least builds would throw an error if they're on the wrong version

[skinny85]

I don't have much typescript experience, would it be reasonable to add a dependency to the core module for typescript ^3.7?

That way at least builds would throw an error if they're on the wrong version

The thing is, you can also work around it by changing noImplicitAny: true to false in tsconfig.json, so throwing an error here would be a little too harsh.

[bo67192]

@skinny85 fair enough.

Is there any better way of letting users know they should double check for this? Maybe in the release notes? We've stumbled into it in two projects so far.

[skinny85]

Not really :( unfortunately, we missed this change when we released it, that's why it's not in the release notes, and hence this pinned issue.

[ghost]

I had a similar error
changing noImplicitAny: true to false in tsconfig.json
delete node_modules folder
run
npm i
next step restart the vscode to effect the changes

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.