Crashes with parseWithProgramProvider related warning

[bebraw]

I set up a demonstration about this: https://github.com/bebraw/styleguidist-ts-sc/tree/parser-bug .

If you run it, you should see

Warning: Cannot parse src/components/ButtonSCTS.tsx: TypeError: Cannot read property 'parseWithProgramProvider' of undefined

kind of warnings. I looked at the and it's crashing at the parser around line this.parseWithProgramProvider(filePathOrPaths) since this is undefined. I tried replacing the call with a regular function and it parsed fine. To fix, likely we have to do something about the way this is bound.

[pvasek]

It seems that the example project is set up in the same way and last time was working fine. I guess there has to be other differences, any ideas?

[bebraw]

@pvasek Just doing yarn install and yarn start against the example project gives a huge amount of type errors to me. Example:

node_modules/@types/prop-types/node_modules/@types/react/index.d.ts:3552:19 - error TS2320: Interface 'Element' cannot simultaneously extend types 'ReactElement<any>' and 'ReactElement<any>'.
  Named property 'type' of types 'ReactElement<any>' and 'ReactElement<any>' are not identical.

3552         interface Element extends React.ReactElement<any> { }

I wonder if we have different versions of Node and Yarn. Could you try running the same? The original issue might be something related to this too. I'm running Node 8.11.2, yarn 1.9.4.

Btw, it would be nice to standardize either on npm or Yarn in the project (just single lockfile to maintain).

[pvasek]

@bebraw Hmm, I am using yarn v0.21.3 and node v10.1.0.

After deleting node_modules I am getting also bunch of "warnings" from styleguidist. Will need to investigate it more. I agree with you regarding yarn/npm lock files.

I guess it would make sense now to use npm while it's used also for styleguidist itself.

[bebraw]

Ok, cool. Thanks for the merge. Let me know if there's any way I can help with the example project issue.