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

Fix npm warnings #78

Merged
merged 1 commit into from Dec 12, 2016
Merged

Fix npm warnings #78

merged 1 commit into from Dec 12, 2016

Conversation

SpaceK33z
Copy link
Contributor

npm is giving these warnings on every npm install:

npm WARN deprecated node-uuid@1.4.7: use uuid module instead
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130

These dependencies are installed by the package request, and upgrading that package should fix it.

npm is giving these warnings on every `npm install`:

```
npm WARN deprecated node-uuid@1.4.7: use uuid module instead
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
```

These dependencies are installed by the package `request`, and upgrading that package should fix it.
@phillipj
Copy link
Owner

Unfortunately there seems to be some differences related to timeouts in newer versions of request, breaking one of our tests. I'm also seen the same as visible in Travis CI run.

Probably something fishy we're doing on our end in combination with request/request#2431. Will have to dig more into what's happening before fixing/merging this.

@phillipj
Copy link
Owner

After fixing the timeout test on master, Travis got happy. Thanks for pushing this update 👍

@phillipj phillipj merged commit 24401e0 into phillipj:master Dec 12, 2016
@SpaceK33z
Copy link
Contributor Author

Awesome!

@SpaceK33z SpaceK33z deleted the patch-1 branch December 12, 2016 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants