'use strict' causing error deep in dependency chain

[dobrite]

This commit of error in 4.3.0 causes an error when in strict mode:

Uncaught TypeError: Cannot assign to read only property 'name' of function createError(opts) {
            var result = new Error()... <more>

The line is here.

Assigning the name property of a function is usually a no-op (non-standard though) but in strict mode it throws.

error is a dependency of virtual-dom.

This is an error that happens when trying to run the example code in the README under chrome with webpack.

I'm thinking the issue might lay with error but am unsure. I filed an issue there too. 😄

[staltz]

If you use a deep 'use strict' then these problems pop up. I don't think we have any alternative than wait for a fix in the dependency.

FYI, the README example is the same as this: https://github.com/staltz/cycle/blob/master/examples/hello/hello.js

[dobrite]

Closing... will carry on conversation in the error repo.

Thanks for taking a look at this!

Happy New Year! 🎉

[sunwukung]

Just for posterity, I raised this issue after encountering the same error.