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

Can you provide the full cli output you're seeing?

```
    Type                 Name                      Plan        Info
     pulumi:pulumi:Stack  analytics-web-production  running     ASSUMING ZONE <http://sub.mydomain.com|sub.mydomain.com>. EXISTS
```
Which comes from a code snippet that looks like:
```
   const domainParts = getDomainAndSubdomain(config.targetDomain);
    console.log(`ASSUMING ZONE ${domainParts.parentDomain} EXISTS`);
    const hostedZoneId = aws.route53.getZone({ name: domainParts.parentDomain }).then(zone =&gt; zone.id);
    console.log("Fetched zone");
 
```

So grpc has problems on Catalina, though I’m not exactly sure what or why, but I had to blow away my yarn.lock to get anything to even run (grpc fails to build). Here’s the diff of the new yarn.lock: <https://gist.github.com/loganb/6df360e2c42d0945ebfe2db7ce80d7a2>

I’m also using a ~6 month old version of this example: <https://github.com/pulumi/examples/blame/master/aws-ts-static-website/index.ts>

Notably, two months ago the line that is blocking for me was changed to “use synchronous data sources” (mine uses a promise), <https://github.com/pulumi/examples/blame/master/aws-ts-static-website/index.ts#L101>

Looks like an issue with Catalina and Node 12. I'm seeing the same thing. I'm opening an issue now. Downgrading to Node 10 (LTS) should resolve it.

<https://github.com/pulumi/pulumi/issues/3309>