Tom MacWright

We should probably add `ts` to requireExtension defaults. https://github.com/documentationjs/documentation/blob/4ea3a95539513029fc1bafddad4e770934b7d019/src/input/dependency.js#L64 Try running with `--require-extension=ts`?

Whoops, try `--require-extension=.ts`? Forgot that there's a `.` necessary.

Could you try to be more specific than "quite weird"? For maintainers, this is really not a very good way to start an issue - there's absolutely no way that...

The glob that I recommended will exclude it.

Indeed, that's true - what's needed is to add config as an argument in the [build method’s jsdoc](https://github.com/documentationjs/documentation/blob/master/src/index.js#L193).

That's unfortunate - if they had chosen to use Markdown syntax in the comment description, it would have been compatible with JSDoc – or if they had just used the...

Sure - the main reason is just the default theme, which uses lodash's template engine.

Super cool! Sure - if you've got the time to refactor it into something PR-able, we'd definitely be into it.

This is a pretty tough area for documentation.js: pipelines don't especially affect the AST in a way that would break its inference, but other parser options would, hence the fixed...

> So I would just make the whole "standardBabelParserPlugins" dynamic, to make the whole thing future-proof. What if for example @babel/plugin-proposal-optional-chaining suddenly allows a new flavour option? Yeah, the issue...