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

Okay, <@UDDF5MPU4>, this is pretty gross but I think it will unblock you.

Can you edit `~/.pulumi/bin/pulumi-resource-pulumi-nodejs` to look like this:

```
#!/bin/sh
node $(node -e "console.log(require.resolve('@pulumi/pulumi/cmd/dynamic-provider'))") $@
```

The change here is that instead of the relative path, we now use `$(node -e "console.log(require.resolve('@pulumi/pulumi/cmd/dynamic-provider'))")` to construct the path where the dymanic provider's launcher is, which will allow node to use its normal resolution semantics.

I believe that will address your issue, based on my local testing it does for me.

I opened <https://github.com/pulumi/pulumi/issues/2261> to track making the actual fix, but I'd love to know it addresses your issue first.

thanks <@U87DZN4MT>, I can check it tomorrow

it solved the issue, at least for the preview, I can't run the actual update right now, but assume it will be ok, thanks <@U87DZN4MT>

Thanks.  I’ll get this into master on Monday.

<@UDDF5MPU4> Just an FYI, I released a new version of the CLI (0.16.7) that has this fix.  Thanks for reporting the issue!