Cannot read property 'getLineAndCharacterOfPosition' of undefined about fork-ts-checker-webpack-plugin HOT 8 CLOSED

I'd suggest clearing your node modules and reinstalling - btw you didn't share your plugin setup..

from fork-ts-checker-webpack-plugin.

@johnnyreilly Thanks, it helped!

from fork-ts-checker-webpack-plugin.

Unfortunately i was wrong. Error just didn't appear until i resolve webpack errors. Plugin configuration is default - just new ForkTsCheckerWebpackPlugin(). Maybe there's some dependency that probably may be the reason?

EDIT: Error starts with [email protected], 2.3.2 doesn't show this error.

from fork-ts-checker-webpack-plugin.

According to this (function logErrors) diagnostic.file can be nil.

Wrapping code inside NormalizedMessage.createFromDiagnostic in if (diagnostic.file) and printing diagnostic i've got in console:

 66% building modules 862/921 modules 59 active ...ct\lib\ReactTransitionChildMapping.js###DIAG { file: undefined,
  start: undefined,
  length: undefined,
  messageText: 'Cannot find global value \'Promise\'.',
  category: 1,
  code: 2468 }
 95% emittingERROR in undefined(undefined,undefined):
TS2468: Cannot find global value 'Promise'.

So maybe reading diagnostic.file attributes should be wrapped in if (diagnostic.file)?

from fork-ts-checker-webpack-plugin.

Thanks for digging into this @nidu. You're seeing:

TS2468: Cannot find global value 'Promise'.

Are you running in a super old version of node?

It would be useful if you could provide a minimal reproduction of the issue; it's hard to know if this is a configuration problem or a bug with fork-ts-checker-webpack-plugin.

from fork-ts-checker-webpack-plugin.

@johnnyreilly environment is as following:

Windows 7x64
webpack 3.10.0
node 6.11.0
npm 3.10.7
typescript 2.6.2
fork-ts-checker-webpack-plugin 0.2.9
ts-loader 3.2.0

I resolved the error by adding es6-promise to the project so this particular error was mine. But at the same time i think checker should print error and errors like this can occur. Moreover according to example from my link above diagnostic.file can be undefined so i suppose nil check is worth adding.

from fork-ts-checker-webpack-plugin.

Yeah that sounds reasonable. If you get a chance to submit a PR I'm sure @piotr-oles would be appreciative

from fork-ts-checker-webpack-plugin.

PR merged, will be released as v0.2.10 :)

from fork-ts-checker-webpack-plugin.