Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
p
prehistoric-laptop-47240
11/24/2022, 4:12 PMHi quick question : Any idea why when using typescript, Pulumi ignores my configuration in tsconfig.json ?
To give more context, I added some typings using
includenpx tsc -p tsconfig.jsonl
little-cartoon-10569
11/24/2022, 11:30 PMIs your Pulumi project in the same directory as tsconfig.json (or a subdirectory)? Have you configured a non-default Typescript setup (https://www.pulumi.com/docs/intro/languages/javascript/#disabling-built-in-typescript-support)?
p
prehistoric-laptop-47240
11/28/2022, 9:37 AMThanks for your answer.
Actually, yes: Pulumi in inside the same folder of the tsconfig.json file. No non-default typescript setup here (version v3.48.0).
I have my monorepo project files and folders, and one folder for "infrastructure" where Pulumi files and custom utils are
Content of Pulumi.yaml :
name: infrastructure
description: A minimal TypeScript Pulumi program
runtime: nodejsContent of tsconfig.json
{
"compileOnSave": true,
"compilerOptions": {
"strict": true,
"outDir": "bin",
"target": "es2016",
"module": "commonjs",
"moduleResolution": "node",
"sourceMap": true,
"experimentalDecorators": true,
"pretty": true,
"noFallthroughCasesInSwitch": true,
"noImplicitReturns": true,
"forceConsistentCasingInFileNames": true
},
"files": [
"index.ts"
],
"include": [
"typings/*.d.ts"
]
}Actually the weird part is, as an example, if I try to set an invalid "target", I have an error so the file is parsed. It's like if the "include" section would be overwriten
Okay, it's due to how ts-node works VS tsc i'm used to. I had to follow a convention as suggested in https://github.com/TypeStrong/ts-node/issues/782