wooden-queen-36575
04/23/2023, 11:48 PM../../../
in my imports, so that I can refer to all my lib
files using an alias from all of my stacks. I've defined the paths in the tsconfig.json
file in the root of the repository, and have additionally referred to this using extends
in a tsconfig.json
file in each stack folder. The aliases aren't resolving, so I'm getting Cannot find module
. Is this kind of thing supported currently?├── config
│ ├── base.template.yaml
│ └── localstack.template.yaml
├── lib
│ ├── components
│ │ └── aws
│ │ └── backend
│ │ └── S3KmsBackend.ts
│ └── utils
│ ├── Stack.ts
│ └── registerAutoTags.ts
├── stacks
│ └── stack-a
│ ├── Pulumi.yaml
│ ├── index.ts
│ └── package.json
│ └── tsconfig.json
│ └── stack-b
│ ├── Pulumi.yaml
│ ├── index.ts
│ └── package.json
│ └── tsconfig.json
├── tests
│ ├── docker-compose.e2e.yml
│ ├── e2e
│ │ └── e2e.test.ts
│ ├── tsconfig.json
│ ├── unit
│ │ └── lib
│ │ ├── components
│ │ │ └── aws
│ │ │ └── backend
│ │ │ └── S3KmsBackend.test.ts
│ │ └── utils
│ │ └── Stack.test.ts
│ └── utils
│ ├── captureConsole.ts
│ ├── env.ts
│ └── s3Helper.ts
├── tsconfig.json
├── package.json
├── requirements.txt
├── Pulumi.yaml
├── README.md
little-cartoon-10569
04/24/2023, 1:30 AMruntime:
name: nodejs
options:
nodeargs: "--loader ts-node/esm --no-warnings"
You can also get tsconfig's paths working. I've had it working in the past, but since we switched to Yarn2, I've migrated everything to use that, and the tsconfig settings aren't needed for that.nodeLinker: node-modules
in your .yarnrc.ymlwooden-queen-36575
04/24/2023, 1:41 PM