-
Notifications
You must be signed in to change notification settings - Fork 36
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
Update rxjs dependency #122
Comments
event-emitter.js:15Uncaught TypeError: Super expression must either be null or a function, not object |
I've confirmed this bug. I updated the package.json to point to 'rxjs' instead of '@ReactiveX'. It's still 5.0.0-beta.0 though. I'm pretty sure it's the call to |
Maybe we should just copy Angular 2's |
Except for some line breaks in that update I did copy the latest version of EventEmitter at the time. It's not liking it. See: d500158 |
Ah, sorry. Did not realize that's where you started. I'll take a closer look. |
That fixed it locally (the {Subject} advice)! I've pushed to the issue-122 branch, we'll see if it goes through CI. |
Hmm... nope... failed. It runs the tests locally... I'm using npm 2, not sure if that matters. |
Tried installing 'rxjs-es' too... and that's failing too. @MikeRyan52 I'm not sure. |
I'm not sure what went wrong with the tests, but the change that maps EventEmitter::emit to Subject::next re-enables that function for me, and is one of two reasons, since it's not in npm, yet, that I'm running from a fork (the other being addressed in #141). What criteria must be met to get to a next npm release? Anything I can do to help it along? Edit: forgot to mention that holding down to In beta.1, rxjs dropped |
Apparently our lib doesn't work with latest rxjs release.
https://www.npmjs.com/~reactivex
The text was updated successfully, but these errors were encountered: