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

Is 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>)?

Thanks 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: nodejs```

Content 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>