-
-
Notifications
You must be signed in to change notification settings - Fork 22
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: Cannot read property 'pipesCount' of undefined #14
Comments
Looks like adding any sort of middleware is enough to break it :(
results in
|
Anyone have any idea about what to do if this happens? |
Just ran into this as well. |
I'm getting this error from an entirely different setup that doesn't even include node-run-middleware. So maybe the problem is deeper - like Express itself. |
I ran into this same issue. Solved by passing the request parameter app.runMiddleware('/handler', {connection: {}}, function(code, data) {
console.log(code, data);
process.exit();
}) |
I solved it by passing
|
this still happens if you have routes configured with sendFile:
I tried every solution proposed above to no avail. |
this worked for me |
Try to delete the response.json() of the api /sessions , it works for me. |
If anyone wants to create a PR to fix it, I will merge it |
I had this issue before I had a catchall route set up to 404. Basically when a url was accessed where no route matched then this happened. Adding a catchall after all other routes were registered (so it only runs if nothing else matched) fixed it in my case. |
I am trying to use run-middleware within an angular-fullstack application.
My application is using express for managing sessions and passport.js for authentication (stored in Mongodb). When a user logins in, I want to check if that user already has a living session. I want to use run-middleware to programmatically query mongodb for all the live sessions.
The error I am getting is:
The text was updated successfully, but these errors were encountered: