This makes sure that we get the name and params from exported
functions/classes/vars.

For export default the name is inferred from the file name.

Towards documentationjs#424

This adds a boolean flag called `document-exported` (defaults to false)
that effectively adds an empty comment to all exported bindings that do
not already have a JSDoc comment. It also goes does the same for the
members of exported classes and objects.

```js
export class C {
  method() {}
}
```

Both `C` and `C#method` are now part of the generated documentation.

Related to documentationjs#424

This adds a boolean flag called `document-exported` (defaults to false)
that effectively adds an empty comment to all exported bindings that do
not already have a JSDoc comment. It also does the same for the
members of exported classes and objects.

```js
export class C {
  method() {}
}
```

Both `C` and `C#method` are now part of the generated documentation.

Related to documentationjs#424

This adds a boolean flag called `document-exported` (defaults to false)
that effectively adds an empty comment to all exported bindings that do
not already have a JSDoc comment. It also does the same for the
members of exported classes and objects.

```js
export class C {
  method() {}
}
```

Both `C` and `C#method` are now part of the generated documentation.

Related to documentationjs#424

* Add a flag to document all exported bindings

This adds a boolean flag called `document-exported` (defaults to false)
that effectively adds an empty comment to all exported bindings that do
not already have a JSDoc comment. It also does the same for the
members of exported classes and objects.

```js
export class C {
  method() {}
}
```

Both `C` and `C#method` are now part of the generated documentation.

Related to #424

* Fix lint error

* Rebase and use options pragma in test file

* Create extractor type as a generalized comment/export getter

* Document exported extractor

…ionjs#424)

* Add initial section for tooling

* Remove unneeded whitespace

* Add some initial updates for core libraries

* Add section for contrib, node, and web libraries

* Add 'replace with Type.Proxy' note

* Drop prepare-0.15 package set note

* Link to es modules script

The above guide doesn't mention the issue with
"use strict"; not getting dropped.
Not sure if we should mention it
here explicitly, but
my script accounts for that.

At the same time, my script
uses bash commands that
may not work the same on MacOS

* Add note about export renaming