Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regenerator v0.4.7 breaks component-resolver #15

Open
dominicbarnes opened this issue May 12, 2014 · 4 comments
Open

Regenerator v0.4.7 breaks component-resolver #15

dominicbarnes opened this issue May 12, 2014 · 4 comments
Labels

Comments

@dominicbarnes
Copy link
Contributor

Not sure what exactly, but there's a breaking change in regenerator 0.4.7, reverting to 0.4.6 fixes the issue, but we should figure out what changed so we can stay up-to-date.

TypeError: Object prototype may only be an Object or null
    at Function.create (native)
    at Empty.Generator (/home/dominic/TreeTop/component/node_modules/component-resolver/build/index.js:69:38)
    at wrapGenerator (/home/dominic/TreeTop/component/node_modules/component-resolver/build/index.js:29:12)
    at Remotes.resolve (/home/dominic/TreeTop/component/node_modules/component-resolver/node_modules/remotes/build/remotes.js:487:10)
    at Resolver.$callee$ (/home/dominic/TreeTop/component/node_modules/component-resolver/build/semver.js:605:46)
    at Empty.invoke (/home/dominic/TreeTop/component/node_modules/component-resolver/build/index.js:148:31)
    at Empty.invoke (/home/dominic/TreeTop/component/node_modules/component-resolver/build/index.js:86:50)
    at next (/home/dominic/TreeTop/component/node_modules/component-resolver/node_modules/co/index.js:83:21)
    at /home/dominic/TreeTop/component/node_modules/component-resolver/node_modules/co/index.js:56:5
    at Channel._call (/home/dominic/TreeTop/component/node_modules/component-resolver/node_modules/chanel/lib/proto.js:114:3)

This error shows up in our Travis build, and I've seen it locally as well.

@jonathanong
Copy link
Contributor

okay the runtime broke backwards compatibility. basically, we would have to rebuild all the components using the latest regenerator at once.

@dominicbarnes
Copy link
Contributor Author

You shouldn't need to rebuild everything, just the ones that have been published with the latest version of regenerator. (only about 10 days old afaik)

@jonathanong
Copy link
Contributor

you do because the runtime is global =/

@dominicbarnes
Copy link
Contributor Author

aaaaaaaaaaaaaaaaaaaaaaaah crap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants