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

What do I miss?

```
pulumi.output(new gcp.compute.Subnetwork("z", {ipCidrRange: "111", network: "zzz"})).name;
```

Error on `tsc --noEmit`:
```
Property 'name' does not exist on type 'OutputInstance&lt;Subnetwork&gt;'.

16 pulumi.output(new gcp.compute.Subnetwork("z", {ipCidrRange: "111", network: "zzz"})).name;
```

property is definitely there: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gcp/compute/#Subnetwork-name>

also strange that error doesn't show full type `gcp.compute.Subnetwork`, but just `Subnetwork`

basically trying to do:

```
const neteng = new pulumi.StackReference(
    "org/gcp-neteng/prod"
).requireOutput("gke01London") as pulumi.Output&lt;gcp.compute.Subnetwork&gt;;


...
neteng.name;
```

and it fails. interestingly this change makes it work:

```
).requireOutput("gke01London") as pulumi.Output&lt;Pick&lt;gcp.compute.Subnetwork,'name'&gt;&gt;;
```

The outputs on `StackReference`s are plain JavaScript objects, not fully realized `Resource` instances.  You typically need to output an id from one stack, and then `.get` that `id` in the other stack.

` as unknown as gcp.compute.Subnetwork;` works, but  I agree that exporting just ID might be better

I've found why it is like this. Basically `pulumi.Output&lt;Resource&gt;` leaves it with `OutputInstance&lt;Resource&gt;`  without `&amp; Lifted&lt;T&gt;` part, that is because of <https://github.com/pulumi/pulumi/blob/8fd05fcd9fbd1480c01726b4fc7fcf158e611f99/sdk/nodejs/output.ts#L685> which skips recursing into object properties with `LiftedObject`. pulumi.Output&lt;Pick&lt;Resource, 'id'&gt;&gt; works because that `extends Resource&lt;T&gt;`  becomes false and it recurses

I'll create an issue for you to decide whether it is a bug , but it is definitely a usability problem

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