Handle re-exports

Some modules re-export members directly. This is also sort of an import.

I.e.

export { default as Foo, Fooz, Foob } from './Foo';
export { default, NonDefault } from './qwe';
export * from './asd';
export * as bar from './bar';

It would be nice if this would be sorted automatically as well following the same rules as imports.

I think this is mostly not combined with regular imports, but it could be. This means there should be rules for this.

Candidate rules I could come up with:

1. re-exports before imports
2. re-exports after imports
3. re-exports mixed with imports

Personally I’d go with 2.

[remcohaszing]

Actually my use case is the simplest one possible. My packages contain an index.ts which re-exports named packages.

Examples:

• https://gitlab.com/appsemble/appsemble/-/blob/master/packages/node-utils/src/index.ts
• https://gitlab.com/appsemble/appsemble/-/blob/master/packages/preact-components/src/index.ts
• https://gitlab.com/appsemble/appsemble/-/blob/master/packages/react-components/src/index.ts
• https://gitlab.com/appsemble/appsemble/-/blob/master/packages/utils/src/index.ts
• https://gitlab.com/appsemble/appsemble/-/blob/master/packages/web-utils/src/index.ts

Also I have moved away from this plugin, because the import/order ESLint rule can do pretty much the same now, works with require, and doesn’t require me to install a separate package. I may want to use this plugin again if re-exports are supported though.

[lydell]

Released in v6.0.0.