{{ message }}
Repository navigation
Compile errors of user of @aws-crypto/material-management with TypeScript 3.7.2 #232
Description
With @aws-crypto/client-node 1.0.1, TypeScript 3.7.2, on NodeJS 12.13.0 I'm getting this error when compiling our own sources:
> tsc && tsc -p tsconfig.es6.json
node_modules/@aws-crypto/material-management-node/build/main/node_cryptographic_materials_manager.d.ts:3:21 - error TS2440: Import declaration conflicts with local declaration of 'NodeEncryptionMaterial'.
3 NodeAlgorithmSuite, NodeEncryptionMaterial, NodeDecryptionMaterial, KeyringNode, GetEncryptionMaterials, GetDecryptMaterials } from '@aws-crypto/material-management';
~~~~~~~~~~~~~~~~~~~~~~
node_modules/@aws-crypto/material-management-node/build/main/node_cryptographic_materials_manager.d.ts:3:45 - error TS2440: Import declaration conflicts with local declaration of 'NodeDecryptionMaterial'.
3 NodeAlgorithmSuite, NodeEncryptionMaterial, NodeDecryptionMaterial, KeyringNode, GetEncryptionMaterials, GetDecryptMaterials } from '@aws-crypto/material-management';
~~~~~~~~~~~~~~~~~~~~~~
Found 2 errors.
tsconfig.json:
{
"extends": "./tsconfig.base.json",
"compilerOptions": {
"outDir": "dist"
}
}tsconfig.es6.json:
{
"extends": "./tsconfig.base.json",
"compilerOptions": {
"module": "es2015",
"outDir": "dist.es6"
}
}tsconfig.base.json:
{
"extends": "tsconfig-collaborne",
"compilerOptions": {
"declaration": true
},
"include": [
"src"
]
}(https://github.com/Collaborne/tsconfig-collaborne/blob/master/tsconfig.json has "tsconfig-collaborne")
Activity
ankon commentedon Nov 6, 2019
Changing NodeJS to 10.16 doesn't change things.
Changing TypeScript to 3.6.4 "fixes" the compile error.
seebees commentedon Nov 6, 2019
Thanks for the report!
fix: Import declaration conflicts with local declaration
fix: Import declaration conflicts with local declaration
fix: Import declaration conflicts with local declaration
fix: Import declaration conflicts with local declaration (#233)
ankon commentedon Nov 12, 2019
If I may ask, what is the rough timeline for a release of the SDK with the fix for that problem?
seebees commentedon Nov 12, 2019
@ankon Released to npm :)