-
Notifications
You must be signed in to change notification settings - Fork 30
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
Upgrade qs dependency #61
Conversation
Previously required version contained a security vulnerability. See flatiron#59 Fixes flatiron#59
Same tests fail with or without this patch...so there's that... Also, the devDependencies are rather old also, and
|
I definitely noticed that with Speaking of tests, on the other hand, the |
I did see that when running in bash (on Windows via mingw), but that (and the others) completed fine (though some failed) when running in |
Yeah it hangs for me on zsh on Linux. Sounds like it's own issue, and like magic it's now #63 |
@indexzero can you take a look at this upgrade? It fixes a vulnerability that effects I'd like to avoid forking Cheers! |
Are there any updates on this PR? |
@hiddensanctum looks like this is blocked on #63 |
@hiddensanctum @shakeelmohamed we need @indexzero to take a look at this, I don't have the power to merge. |
@thornjad thanks, I've sent him a kindly worded email. Let's see if that helps make some progress 😃 |
@BigBlueHat made you an admin of this to support the work you do in |
Published in In a streams3 world, it serves no purpose. |
Union is not actively developed anymore, see [1]. Union provides a middleware capability similar to connect [2] supporting buffered streams and providing some convenience APIs on top of the middleware capability. However, the stream functionality offered by union is already available since Node.js v0.12 [3] and Tabris CLI does not use most of the APIs union offered. Migrate middleware handling to connect. Opt for connect instead of express, since Tabris CLI does not use most of the extra features express offers and express comes with significantly more external dependencies (currently connect 4 vs express 30). Error handling notes: * connect errors do not have a status field. Only log the error message. * connect does not handle 404 as an error as union did. Restore this behavior by using an extra middleware to catch all unhandled requests and treat them as errors. [1]: http-party/http-server#138 (comment) [2]: https://www.npmjs.com/package/connect [3]: flatiron/union#61 (comment) Fix #71 Change-Id: If502571e61f53098afd6cbfbfa66e8053691eeda
Previously required version contained a security vulnerability. See #59 and https://snyk.io/vuln/npm:qs:20170213