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

The second error is
```error TS7053: Element implicitly has an 'any' type because expression of type '0' can't be used to index type 'Output&lt;string[] | undefined&gt;'.
  Property '0' does not exist on type 'Output&lt;string[] | undefined&gt;'.

           resource.propertyOfTypeOutputStringArray[0].promise(),```

Not much changed in this version; <@UHTP242EB> could it have to do with this?
&gt; * Upgrade to v2.15.0 of pulumi-terraform-bridge &amp; v2.15.0 of pulumi/pkg and pulumi/sdk
&gt;     * These changes introduce enums to the Go and Python SDKs.
&gt;     * This introduces package/module registration for NodeJS and Python.

Another possibility is the change in transitive dependency to pulumi ^2.15.0, which is pulling in 2.15.4. With pulumi-aws 3.17, the dependency is ^2.0.0 which is pulling in 2.12.1.

Ah, that changed the dependency on node from 10.0 to 14.0. Betya that's the issue..