npm package request deprecated

[jasperchua99]

request/request#3142

this npm package seam to be deprecated, any reification to use another package?

[TobiTenno]

Sadly, the owner didn't give me sufficient perms to merge my own fixes and no one else can review my changes. So until some configuration on this repo gets fixed, I can't fix that and some other outstanding issues.

[jasperchua99]

oic

[filipedeschamps]

You guys are right. After others projects and a recently born son my life has changed significantly. I've also published a video on my channel explaining how I screwed up with my open source projects.

But what can I do to fix this? @TobiTenno you have write access to the repo I think, maybe you can start merging things to master by yourself, you are doing an amazing job. And I saw you made a PR to start using Github Actions. What do you think to remove all external dependencies (including Coverals)? Also, let's not auto-publish do npm. I prefer doing this manually.

[TobiTenno]

I think admin is required to merge my own and set up better actions.

my reasoning on auto-publishing is that it keeps fixes going out quickly (and I don't have access to do so), so it would make it easier on you and I so that in the future if others are brought on to approve, they don't also need access to publish. the keys are thankfully secrets and github doesn't allow reading them after they're written, so even I would never need to know the npm token's contents

i still think this is an awesome project and I'd love to keep it going as much as I'm able. Stuff like coveralls or codeclimate are fine to me because they give an extra eye to security checks that I might not realize. there are github actions that can do some of the same, but I've not seen one for coverage as of yet.

[jasperchua99]

well im all ears to hears what yall are gonna do to make sure this project goes smoothly, for now tho, request is the only one bugging my npm to change to another file

[TobiTenno]

Yeah, I'll get started on that migration once I finish the 2 others (config spread and dedupe)

[TobiTenno]

at this point, i'm gonna have to lean on y'all, cause I can't merge my own stuff still, so if y'all can submit fixes, i can merge them

[sankemax]

@TobiTenno hey, if i create a PR, will you merge it?

[TobiTenno]

If it works, yes

[TobiTenno]

@sankemax would you be down to help me by basically resubmitting several of my old PRs that include things like reducing config spread and moving to gh actions? I can help manage more PRs and get more updated off of travis and deprecated deps

[TobiTenno]

@filipedeschamps we really need you to do those parts switched out on #216. it would be even better if you turned this into an org project and migrated it there, that would give you and i equal access to the configs and i'd be able to merge my own PRs without waiting for approvals, just for CI to merge

[filipedeschamps]

Done @TobiTenno 👍