Tom MacWright

Like #1099, I don't think this is a good idea: it would degrade turf-meta performance just in order to make it 'easier' for core contributors. turf-meta is low-level code: it...

We don't really support the `@module` tag at this point, because it doesn't have a clear meaning; JavaScript has npm modules, and it has ES6 modules, and the JSDoc concept...

In isolation (taking this example code and closing the } to get it syntax-valid), I'm not able to replicate the issue. I'll try with the main repo.

The issue is with module dependency resolution, which is implemented by [detective](https://www.npmjs.com/package/detective), a dependency via module-deps, which is lovely but woefully vintage. To work around, you can run ``` documentation...

This looks to me like intended behavior - [the JSDoc spec doesn’t mention anything about properties having default values](http://usejsdoc.org/tags-property.html).

Does this project have any JSDoc annotations, or `/**` comments at least? Perusing [the project](https://github.com/zerobias/effector/blob/master/src/effector/domain/domainFabric.js), it doesn't look like it has any documentation markup.

By [creating a documentation.yml file!](https://github.com/documentationjs/documentation/blob/master/docs/CONFIG.md#configuring-documentationjs), you can manually organize documentation any way you want! Unfortunately it doesn't yet affect Markdown output yet ([tracking that issue here](https://github.com/documentationjs/documentation/issues/615))

Hi Kasper, > I've had a go at passing through a jsdoc.json config file to the linter but it does not seem as though it reads JSDoc configuration. Yep, that's...

I'm still not completely clear on the intent here - of your or Kasper's suggestions. What would `component` do? How would it be different than `@module`? How would `@slot` work?...

Yep, this'll necessitate switching away from `require.resolve`, maybe using [resolve](https://www.npmjs.com/package/resolve) instead in this case.