import contentful from 'contentful' changed behaviour

[grncdr]

When we moved to ES6, users of this library who are also using Babel get subtly different behaviour when importing. Now when you import contentful from 'contentful' you don't get an object containing all exported functions, but rather the (non-existant) default export from this library. We need a backwards compatible export default statement.

[wmadden]

@grncdr related to this topic, users who're compiling Contentful from source will also be hit by the "bug" in axios that it imports and forcefully polyfills the global Promise implementation with the es6-promise polyfill.

This caused problems for us because es6-promise won't handle errors that aren't caught in a call to catch() at all - they just get eaten.

[rossthedevigner]

Just came upon this issue today... 1.1.5

[trodrigues]

Keeping an eye on the next release of axios which will fix the issue.

[trodrigues]

Created #44 to track that.

[trodrigues]

Fixed on 2.1.0.