Following the https://github.com/pulumi/kubernetes-the-prod-way, I have multiple stacks. I’m a well versed typescript user and that is one of the draws to the pulumi stack. In trying to reuse some code, as well as change and put

src

elsewhere, I have quickly found out that the

pulumi

cli does not respect the tsconfig.

is it executing ts-node? executing tsc then executing node?

not quite sure what I’m looking at here but trying to help myself 🙂 https://github.com/pulumi/pulumi/blob/master/sdk/nodejs/cmd/pulumi-language-nodejs/main.go#L76

I could be wrong, but my understanding is that since we set these, ts-node won’t pick up the

compilerOptions

specified in tsconfig.json….

However, it’s possible to still setup a system where you manually run

tsc

to generate JavaScript, and just have Pulumi run the generated JavaScript file.

My experience is that pulumi doesn’t read it at all. Proven by doing something as simple as changing the

include

to use a

src

directory instead of at the root

I use ts-node cmd line, I’ve never used it via the api like the pulumi cli does.

I’ll try a ts-node cmdline test

the other pulumi stacks package.json reference them with dependency

"@acme/pulumi": "link:../pulumi",

there is no need for tsconfig-paths

I stuck a sample file in the shared code dir

cloud/pulumi/src

such as

test.ts

with

export const test = () => 'foo'

then a

testIt.ts

in the stack dir and just attempt to run it with

ts-node ./testIt.ts

once that works, you know you have your tsconfig/package.json’s setup

note that yarn uses

link:

while npm uses

file:

- the package manager semantics matter here

since pulumi doesn’t register

tsconfig-paths

you probably want to get tested/setup to run without it

my shared code `package.json`:

{
  "name": "@acme/pulumi",
  "main": "lib/cjs/index.js",
  "typings": "src/index.ts",
  "license": "UNLICENSED",
  "scripts": {
    "build": "../../node_modules/.bin/tsc"
  },
  "dependencies": {
    "@pulumi/gcp": "^0.17.0",
    "@pulumi/kubernetes": "^0.21.0",
    "@pulumi/pulumi": "^0.17.1",
    "@pulumi/random": "^0.5.0",
  }
}

my shared code package

@acme/pulumi

tsconfig.json

is effectively:

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es2015",
    "jsx": "react",
    "lib": ["es2017", "esnext.asynciterable", "dom"],

    "allowSyntheticDefaultImports": true,
    "declaration": true,
    "declarationMap": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": false,
    "moduleResolution": "node",
    "noImplicitAny": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "noEmitOnError": true,
    "noUnusedLocals": false,
    "strict": true,
    "sourceMap": true,
    "suppressImplicitAnyIndexErrors": true

    "outDir": "lib/cjs",
    "rootDir": "src"
  },
  "include": ["../../../js/typings/**/*", "../../typings/**/*", "./src/**/*"],
  "exclude": ["node_modules", "./lib"]
}

I wouldn't think I would want to be setting any

build

in

package.json

in my case.

so you cannot rely on them for executing the

pulumi *

commands

This may be a different problem than the one you solved

you have to

-r tsconfig-paths

to use

paths

with ts-node, so you will need to figure out how to make pulumi’s use of ts-node via api register

tsconfig-paths

Thanks for the help.

Actually got

tsconfig-paths

to work with no modification to pulumi

register with an env var?