Issues with the definite assignment assertion modifier and `strictPropertyInitialization`

[matt-tock]

Hi guys,

TypeScript 2.7 was released recently. They added the strictPropertyInitialization check, which requires the use of the ! definite assignment assertion in some scenarios. atom-typescript is currently spitting out some weird errors when I'm using it. See attached images.

Any thoughts on ways I could fix this? Happy to provide more info/a simpler base case if need be. Thanks!

[lierdakil]

Atom-typescript ships with typescript 2.6.2 at the moment I think, but it can use typescript 2.7 from node_modules. npm install typescript in your package directory?

[matt-tock]

Ah, yea it looks like it's defaulting to 2.6.2. I'll see if I can't get it to recognize the project's typescript installation. This is slightly complicated by the fact we've actually got several projects in the same repo and the node_modules isn't at the root of the directory.

Thanks for the suggestion!

[lierdakil]

Atom-typescript uses Node's module resolution algorithm to look for TypeScript (as implemented by resolve package). So you have some options.

If all else fails, it also respects NODE_PATH.

[lierdakil]

We finally updated bundled TypeScript to v2.7 in atom-typescript v12.4.0