-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
TypeError: Object #<Object> has no method 'removeListener' #462
Comments
If it helps, I only started getting these errors after upgrading to node v0.10.0 (previously on v0.8.18). |
Hrmm.... I haven't gotten these errors with 0.10.1, how about you? |
I upgraded to v0.10.1 this morning and have still seen a couple of these error go past. |
Looked into it, the error is definitely thrown in the node code - it points to the |
Also cleanup unnecessary use of "self" since it will always be called using .apply() from emit.
Fixed/worked-around the node.js change in bal-util v1.16.13 Reinstall docpad with the |
- v6.26.2 March 23, 2013 - Fixes `TypeError: Object #<Object> has no method 'removeListener'` - Thanks to [Steven Lindberg](https://github.com/slindberg) for [issue #462](#462) - Can now customise the `watchOptions` that are used to construct the [watchr](https://github.com/bevry/watchr) instances we create - Updated dependencies
- v6.26.2 March 23, 2013 - Fixes `TypeError: Object #<Object> has no method 'removeListener'` - Thanks to [Steven Lindberg](https://github.com/slindberg) for [issue #462](#462) - Can now customise the `watchOptions` that are used to construct the [watchr](https://github.com/bevry/watchr) instances we create - Updated dependencies
- v1.16.13 March 23, 2013 - `balUtilEvents` changes: - `EventEmitterEnhanced` changes: - Now works with `once` calls in node 0.10.0 - Closes [docpad/docpad#462](docpad/docpad#462) - Changed `emitSync` to be an alias to `emitSerial` and `emitAsync` to be an alias to `emitParallel` - Added new `getListenerGroup` function - `balUtilFlow` changes: - `fireWithOptionalCallback` can now take the method as an array of `[fireMethod,introspectMethod]` useful for pesly binds
Been getting these errors a lot since v6.25.0 on the balupton and docpad websites. Need to be fixed, but I'm not yet sure what is causing the problem.
The text was updated successfully, but these errors were encountered: