Fix: update to babel 6

[hekike]

The current build on npm is not working with projects with Babel 6.x.

• update to Babel 6
• use Object.assign instead of object-assign

[alexkuz]

babel-runtime should stay in peerDependencies, I guess.

[hekike]

@alexkuz why? Actually, I published the current version to our private npm temporary. It's working great.

[alexkuz]

It's working because you're already having babel-runtime it your project (I suppose). It shouldn't be in dependencies, indeed, but the project is still depending on it, so it's has to be in peerDependencies.

[hekike]

@alexkuz I didn't find "official" information about babel-runtime.
However this article is helpful:
http://jamesknelson.com/the-six-things-you-need-to-know-about-babel-6/

So I think it's working because:

The --external-helpers option is now a plugin. To avoid repeated inclusion of Babel’s helper functions, you’ll now need to install and apply the babel-plugin-transform-runtime package, and then require the babel-runtime package within your code (yes, even if you’re using the polyfill).

It's your library, so your decision to do it and apply peerDependency or not.
What do you think?

[alexkuz]

@hekike oh, I see. As far as I understand, now babel is not externalizing helpers with "optional": "runtime" option, so they are included in lib (that's why it's working in your project). We should use babel-plugin-transform-runtime and add "plugins": ["transform-runtime"] to .babelrc - and again, add babel-runtime into peerDependencies :)

[hekike]

@alexkuz done :)

[alexkuz]

Cool, thanks!