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

are you creating ComponentResources? life gets a whole lot easier if you do that, you can just do `npm install ../common/fargate_webapp/`

Well, I think I’d have the same issue. The “common” lib would have to have the providers installed by version, right?

Ideally, they’d only be referenced as PeerDeps.

Sure, I could wrap the creation of my providers in a ComponentResource and return them as outputs. Not a bad idea. :stuck_out_tongue: Was just exporting functions that return the providers.

with a ComponentResource you can create your own package with provider versions for each Component

or are you trying to keep the same version across all?

Yea, that’s the idea. The lib doesn’t specify a version; just implies the consuming project has them installed.

<https://nodejs.org/es/blog/npm/peer-dependencies/>

hrm not super familiar with that, will do some reading and see if I can come up with an answer

Ultimately, it’s just the version of the SDK, not the actual provider runtime version, yeah?

That said, I don’t want to run into this version conflict scenario, cuz our libs and consuming projects *will* get stale. :stuck_out_tongue:

the provider runtime and sdk should be the same