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

Hi there John,
We use custom types and interfaces across a number of projects, that we're referencing using relative paths (I come from the python world so I couldn't say how idiomatic our approach is).
```|_ components
   |_ kubernetes
   |_ DB
|_ models (this is where our types live)```
As for exports, my team and I are rather parsimonious so to speak: we're exporting outputs required to provision resources that are somehow related. Though it is possible to export complex objects, I would rather export simply strings, thereby preventing users from gaining access to protected/confidential resources. Does that make sense?

It's usually best to stay away from exporting types with constructors that have side effects. If you exporting simple JSON objects, you're fine.