Joe Wollard

Can confirm the `usage` issue. I'm using `docs-custom`, not `docs-json` but I suspect the same code is responsible for the issue in both places. With `docs-custom` it seems that watch...

Example of this is ```typescript interface IProps { onChange: (event: React.ChangeEvent); } ``` ... this will render as `(event: any) => void)` with `import React from 'react'`, but renders properly...

@dizel3d - Thanks! That did the trick! I thought I'd specified that, but it turns out I'd only specified it for `ts-loader` and forgot to add it to `react-docgen-typescript-loader`.

I haven't looked it over thoroughly yet, but I'll do my best to get this moving along this week.

@dnicolson / @oliverschwendener - found some additional issues and ended up covering much of what was in this PR. Could either of you try v1.4.0 (simple-plist@next) and let me know...

@dnicolson I'm not able to reproduce that. Is that in a clean project? I'm wondering if there might be some stale caches laying around on your local or something strange...

hmm...now that I've cleared my own caches I'm seeing similar errors, though not identical for some reason. I'll keep poking around a bit to see what I can find.

@dnicolson - I'm still having trouble reproducing that exact error, but I've just published `1.4.0-0` which moves the `@types/plist` package to the dependencies instead of devDependencies. That seems like it...

I just started using Deno for another project of mine and this exact issue crossed my mind. I'll target https://deno.land/x support for the next release.

I couldn't quite get skypack to work for me, but esm.sh with v1.4.0 works. Granted I don't know much about either service, but it seems like esm.sh is automatically injecting...