Anand Eng-Thakker

> At least this morning, I wonder about having custom data as a possibility, not custom tags. Completely remove the expectations of tags, and just say "well, you can throw...

I think it'd be nice to be able to use both multiline and single line comments, and for multiline, both: ```js /* * framed */ ``` and ```js /* bare...

> I think 'any comment that precedes a chunk of exported code' being documentation is doable. Yeah, maybe with the addition of (a) a way to explicitly omit a chunk...

I think another feature of the ideal solution would be that, when documenting flow or typescript code, you don't have to explicitly write type names in documentation comments when they're...

@thejameskyle can you say more about what you don't like about being able to document params in the outer function comment? Asking because I definitely dig the more 'inline' styles...

Note that in flow, I think the only way to do this for standalone functions is to use an intersection type on a function expression: ```js const minus: ((number, number)...

doiuse makes use of the `browserslist` package here: https://github.com/ai/browserslist I'd be happy to accept a PR adding this to the docs. On Thu, Mar 9, 2017 at 8:23 AM thany...

Just published 2.6.0 -- thanks for the heads up @stevewillard

@Haroenv hmm - what are your node and npm versions? `node -v` and `npm -v`

Ah, whoops! Sorry! No super specific theories here, but I'll see if I can reproduce with that node/npm version later.