Upgrade underlying jsdoc

[75lb]

Jsdoc version 3.5.0 was released recently which is able to parse any ES2017 code without the need for Babel plugins. This will mean jsdoc2md users will no longer need to follow the process described here.

I'm testing v3.5.3 with jsdoc2md now, there are a few issues but no blockers. A new jsdoc2md release is imminent.

I'm also considering dropping the --html feature as it gets little use.

[75lb]

I published a pre-release which uses jsdoc@^3.5.3. Generally it works fine but I've found a few differences in output which i'm reviewing. Please try it for yourself and let me know if you find any issues.

$ npm install -g jsdoc-to-markdown@next

[75lb]

Has anyone had time to test jsdoc-to-markdown@next? Does everything working ok?

@victusfate @hydrabolt @weizhongtan @IUnknown68 @wemakeweb @beejjacobs @arronhunt

[beejjacobs]

I've been using it in my module here without any issues.

[75lb]

Fixed and released in v4.0.0 👍

[Rybadour]

I'm confused, you're still using jsdoc-parse 3.0 doesn't this mean it's still using jsdoc 3.0? I've recently ran into a problem with "export class" not being recognized as an ES6 class. This appears to be fixed in JsDoc 3.5. Thoughts?

[75lb]

jsdoc2md uses jsdoc-api, which uses jsdoc v3.5.. exporting values from ECMAScript modules works fine.. examples here.