-
Notifications
You must be signed in to change notification settings - Fork 212
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 libs #86
Upgrade libs #86
Conversation
6916b5d
to
a60d27c
Compare
@nijikokun Is this project still alive? |
Hi @quilicicf taking a look at this now <3 Thank you for submitting! |
'0.0.0.0', | ||
'1.1.1.1' | ||
] | ||
for: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only change that I think we need to address in a future PR, where we resolve back to an array of IPs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything outside of the IPs change looks good, nice work.
Hi,
I installed mockbin and saw it had a few vulnerabilities. I've done all I could to resolve them by upgrading the libs.
Two remain (from
forwarded-http
&jstransformer-marked
) that I can't remove from this repository, I'll try to commit to their repos if I can find the time.Don't be afraid of the amount of changes
I almost only changed lib versions. There isn't 12k editions from me 😆
A note on CI builds
I noticed the Travis builds run on outdated versions of NodeJS (0 -> 5). They should be bumped to supported versions (10 -> 13) IMO. I can edit the
.travis.yml
if it helps but I think it's not my place to decide which versions should be used.EDIT: on second thought, the tests don't run anyway because the version of NodeJS is too old. I'm gonna go for the supported versions and let you update this PR if this is not satisfactory.
A note on tests
I fixed the tests, there were two issues:
/ips
that failed on master too but that I corrected. Please review carefullyafter
phase in the cycle to close mockbin so the tests end gracefullyA note on jade
I upgraded Jade to Pug (it changed name in version 2 for copyright reasons). I successfully loaded the page
index.pug
on my machine so I think I did not break anything but you may think of a better way to test this ?Security audits
The security audit went from:
To: