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

actually, I can provoke the same error in another code-file by just adding:
```export interface ITest 
{
    get name(): string;
}```

I will work around this for now by converting all the getters into methods, but why is this a problem? is there some setting I can change to allow getters?

Is the `get` syntax specific to a particular version? Check which version is defined in your package.json. Also, the default TS configuration uses es2016; was it in there? You might have to override that. See more here: <https://www.pulumi.com/docs/intro/languages/javascript/#3-create-tsconfigjson>

it seems to me that I used the `get and set` syntax 5+ years ago, and tsconfig says only this:

&gt; "compilerOptions": {
&gt;         "strict": true,
&gt;         "outDir": "bin",
&gt;         "target": "es2016",
&gt;         "module": "commonjs",
&gt;         "moduleResolution": "node",
&gt;         "sourceMap": true,
&gt;         "experimentalDecorators": true,
&gt;         "pretty": true,
&gt;         "noFallthroughCasesInSwitch": true,
&gt;         "noImplicitReturns": true,
&gt;         "forceConsistentCasingInFileNames": true
&gt;     },

also, I'm using VSCode, which in turn honors tsconfig. and VSCode is perfectly happy with the get declarations.

so, I think this is maybe something I should create an issue for