Gerrit Birkeland

This would be a breaking change, since plugins are loaded in `Application.bootstrap` which is currently not async, but it seems like a reasonable approach to me.

I like keeping it simple, this is a pretty minor breaking change.

So... I looked at doing this, and it's not something that I want to commit to in 0.22. I'm fine with the breaking change, but it seems that doing this...

I'm not sure I want to add more special casing into the options parser... TypeScript does a similar thing, with a better error message when you do `npx tsc --paths`...

Currently no, not supported. That key only lets you set the name/entry point/readme. PR welcome if you'd like to add support for that though :) src/lib/utils/entry-point

One thing to note: that section of the package.json is only used in packages mode.

Can you set up a repro? This looks to me like `SomeCustomTheme` is undefined

Parameters are already doable - it just requires that you provide a custom `requiredToBeDocumented` that includes `Parameter` https://github.com/TypeStrong/typedoc/blob/98841f5b6c79a2314f5bde6d328fe0b6f4e56bea/src/lib/utils/options/sources/typedoc.ts#L346-L378 Return values are... more annoying. They don't get a reflection of their...

Yes, you can do that, if you give TypeDoc a path starting with `.` it'll look for the file relative to either cwd (if give on the command line) or...

I think I'm going to leave this one to plugin space. There's really not any difference between: ```ts /** Returns the lowest non-negative number in nums */ export function f(nums:...