No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

How are you importing the provider and instantiating it?

<@U012UJTT55M> Like this:
```import {MyResource} from 'my-module/myprovider';

;; ...

const myResource = new MyResource(..., ...);```

You're invoking it with a `new`, so the error message makes no sense to me. Are you exporting a default?

This is how I define my resource class in the module:
```export class MyResource extends pulumi.dynamic.Resource {
    constructor(name: string, args: ...) {
         super(myProvider, name, args);
    }
}```

What I found on the net is that this issue might occur  when a class compiled to ES6 is extended by code that is then compiled to ES5. But I have es2016 in the target in tsconfig.json in both - the module and the pulumi program

<https://stackoverflow.com/a/51860850/13536361>

When I look at the js sources compiled from ts sources, in my case it’s actually the opposite: the code creating MyResource instance in the pulumi program uses new MyResource, but in the module transpiled from ts to js, it does `_super.call(…)` instead of `new Resource`.