make all exports explicit by making them named exports

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

In the context of named vs un-named or default exports, I think we should standardize on a consistent method, which I woudldfavor as named exports.

Some examples, at least in CommonJS where it is most prevalent right now

Unnamed

const name = 'owen';

module.exports = name;

// usage
const anything = require('./name');

Named

const name = 'owen';

module.exports = {
  name
} 

// usage
const { name } = require('./name');

Details

The main case for named being is that everything is consistent everywhere. With un-named, how a user imports a plugin could vary from project to project since the name is left up to the user to decided. For find / replace and refactoring, this could be a real pain, say as part of an upgrade or migration.

Plus it will keep documentation consistent as well.

[thescientist13]

this was handled as part of #707 , so will be available in the next minor release.