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

One way you could get this done relatively simply and quickly is to publish your config types as a package and install as a dependency in your projects? Or publish your parent stack as a package as well and pull the types in from there? 

Yes that's what we're doing. The problem is using the type in two places: the two uses of the type are sufficiently different that it's not worth using the same type in both cases.

I have no trouble publishing an NPM package with the correct type for use in dependent projects. The problem is using that type in the same project as I'm publishing it from: it's just not similar enough.