@Types are stored as dependencies in package.json causing conflicts

[richardspence]

@types are stored as dependencies in package.json causing conflicts.

These conflicts are due to @types/node being added which may conflict with the locally defined global variables.

They should be moved to the dev dependencies.

[Gerrit0]

We should definitely fix this before the next release. Should be a really simple fix.

[aciccarello]

I believe these are actually needed for TypeDoc to be fully typed as a dependency. Blake Embrey, who has done a lot of work around types has been pretty adamant about that. It'd be great if this weren't true because of the conflicts with local types but my understanding is that they need to stay as direct dependencies. Please let me know if there is a better solution.

Duplicate of #408 #335 #350 #384 #418, #434, and #600

Please see those issues for discussion.

[Gerrit0]

The more you know...

Again, this is not about compiling the typedoc package. This is for other people using it programmatically with TypeScript. - Blake

I'd like to take a closer look at this. I don't believe anything from @types/shelljs is actually exported by TypeDoc, so it shouldn't be required. Unless we export types that are imported from one of these modules, they shouldn't be included. We use fs-extra internally, but I don't think it is exported so it shouldn't be included.

[richardspence]

Another option is to split the package.

Have typedoc have the optional dependency of @types/typedoc so consumers can install the later if they require strongly typed programatic access.

Having typedoc install typings is overly opinionated and have burdensome repercussions for consumers esp when CLI use is desired.

[aciccarello]

Those are good points. I agree that it is burdensome and would like to fix it. I'd need to dig into the use cases more but I like the idea of trying to move the non-essential @types dependencies.