Directly importing a type leads to exception

If I try to do this

import { Table } from "@pulumi/aws/dynamodb";
new Table(...);

rather than this

import * as aws from "@pulumi/aws";
new aws.dynamodb.Table(...);

I receive the following error

Running program '...' failed with an unhandled exception:
    TypeError: Class extends value undefined is not a constructor or null
        at Object.<anonymous> (.../node_modules/@pulumi/cloudwatch/eventRuleMixins.ts:70:55)
        at Module._compile (module.js:573:30)
        at Object.Module._extensions..js (module.js:584:10)
        at Module.load (module.js:507:32)
        at tryModuleLoad (module.js:470:12)
        at Function.Module._load (module.js:462:3)
        at Module.require (module.js:517:17)
        at require (internal/module.js:11:18)
        at Object.<anonymous> (.../node_modules/@pulumi/cloudwatch/cloudwatchMixins.ts:16:1)
        at Module._compile (module.js:573:30)

I assume this is an import ordering issue and might not be something we can fix. If it is fixable, however, that would be nice, as the former import style is preferable sometimes.

[jwarwick-delfi]

+1, still an issue on pulumi v3.43.1 with “@pulumi/aws”: “5.17.0”

[andrewdibiasio6]

Any updates on this? I am also having this issue.