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

Generally: don't export objects from the Pulumi program.

The `private` flag is just a TS thing. It doesn't affect anything at runtime. Try the new `#` prefix that is a real private field for JS
<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields>

But I would still not generally export entire instances, make an object just with the properties you want to export:
```export const componentFoo = {
  propA: foo.propA,
  propB: foo.propB,
};
```
I prefer this way, but you can try the `#` field (I never tried, but I think it should work)

Yeah that makes sense. Though honestly the Component was actually the unit of composition and encapsulation I was hoping I could use as "what should be shared".

Feel like it might fit in with the scope of a component to more explicitly define it's output interface. Will try find time and draft a feature proposal

I don't think it would be feasible. Too much happens in ComponentResource constructors. It's unlikely that a stack reference could construct a ComponentResource without side effects.

And you certainly wouldn't want the resource to be constructed in two projects / stacks.