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

I’m attempting to use tsconfig paths, it appears I needed to yarn install with:
```  "resolutions": {
    "cloud-common": "workspace:*"
  }```

tsc was unhappy without the `yarn install` first, just wondering what others are doing with common code that is unpublished…

I’m still trying to iron out tsc/path errors, but curious if others are using separated project/common code amongst stacks and the method used

tsconfig paths are working, for the versions from the last couple of months iirc.

We are using Turborepo with yarn workspaces to manage our monorepo. It currently has close to 10 Pulumi stacks, each implemented as a distinct Node package and most of them consume a shared "utilities" library.

Minimal sample: <https://github.com/ersenal/pulumi-turborepo-micro-stacks>

I did figure out a trick, setting up the `package.json` like this works for `lint`, `tsc`, and `pulumi` without having to run an explicit build (use src ts only), making it far more convenient:

```  "main": "src/index.ts",
  "typings": "src/index.ts",```

^^ also doing it this way with yarn workspaces, I did not need any tsconfig paths.  I add a top level `resolutions: { "my-shared-pkg": "workspace:*" }` and good to go