Docma currently supports JSDoc v3.4.3 (latest stable version as of Jun, 2017).

Static methods (and getters/setters) would work but static (property) fields seem a stage-1 proposal which is currently not supported by JSDoc yet.

Once JSDoc supports it, Docma will.

Thank you,
I supposed it was a jsdoc issue. Even if not supported I hope there is a solution to avoid documentation generation to crash, because it is the automatic conversion suggested by facebook to migrate to react 15 that uses that syntax to autobind functions.
We would try to find a solution to propose to acorn / acorn-jsx (the JS parser at the end of the chain) they can accept.

That crash/issue (with your static property example) is fixed by JSDoc v3.5.4 which is the version Docma will run with the new release.

This will also add support for arrow methods and code with most ES2015 features.

I still have some work with the new release; but won't take too long though.

@onury any idea when a new version will be released.. I thought it would be as easy as just updating the jsdoc-x dependency but its still failing for me on arrow functions

const example = () => { } 

causes an error on page load which results in a no render

Uncaught TypeError: Cannot read property 'indexOf' of undefined at app.min.js:1 at Array.reduce (<anonymous>) at app.min.js:1 at Object.dust.filter (docma-web.js:4) at Chunk.reference (docma-web.js:4) at body_0 (docma-web.js:27) at load (docma-web.js:4) at Chunk.partial (docma-web.js:4) at body_33 (docma-web.js:27) at Chunk.section (docma-web.js:4)

There are other things to be updated such as jsdom which itself also has breaking changes. I'm working on v2 (actually these are implemented already), just needs some more time for template adjustments, etc..

Supported in Docma v2.0.0.
Thanks.