Object.entries is not a function

[x1a0]

After using components instead of component property for my routes I got this exception in browser (Chrome). Server-side-rendering is OK.

This happens in both 0.1.13 and 1.0.0-rc2.

[lostthetrail]

Object.entries is a draft ES7 feature. Check your configuration for ES7 usage.

[sars]

@lostthetrail I thought Babel should care about this ...
hm... looks like a bug.

[x1a0]

@lostthetrail I think as a library it should not require such config on projects that use it. The published codes should be transpiled.

[sars]

the code inside lib npm package includes transpiled version...

[dustinws]

Hi @sars!

While babel does transpile syntax features, it doesn't do a thing for new builtin methods. Those require the use of a polyfill.

Here is a screenshot of the distribution file in lib, you can see that the code is still using the Object.entries method.

This requires the user to bring their own polyfill, which can add a significant size boost to their production builds.

I think it would much more convenient as a consumer of the library for things to just work out of the box.

Thanks!