Fix ambiguity of export default {}

[i-like-robots]

I'm assuming this is an error rather than by design, but I'm not sure...

What

The JavaScript entry point for this module has a default export of an object containing its API methods (export default { ... }). I've assumed that the intention of this was to provide the methods as named exports which can be imported individually, e.g.:

import { getCurrentLayout } from 'o-grid'

However this would currently require destructuring twice as shown below (please note that I've expanded the first line, the shorthand import x from 'y' is syntactical sugar for this):

import { default as oGrid } from 'o-grid'
const { getCurrentLayout } = oGrid

Inconsistent usage has been enabled by transpiling and bundling tools such as Babel and Webpack which supported module syntax loosely but are now moving towards closer spec compliance (see https://github.com/babel/babel/issues/2212#issuecomment-131110500 and https://babeljs.io/docs/en/v7-migration-api#export-changes)

Details

Assuming the intention was for these methods to be named exports I believe the source code should be updated to use the named exports syntax.

[i-like-robots]

It's used as a default export here:

• https://github.com/Financial-Times/alphaville-ui/blob/master/main.js
• https://github.com/Financial-Times/next-article/blob/master/client/components/comments/index.js
• https://github.com/Financial-Times/o-footer/blob/master/src/js/layout.js
• https://github.com/Financial-Times/o-chat/blob/master/src/javascripts/WidgetUi.js

And as a named export here:

• https://github.com/Financial-Times/n-messaging-client/blob/master/src/components/bottom/app-promoting-banner/main.js

So this would indicate sticking to using a default export for the current major version to maintain compatibility.