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
Replace @hapi/shot with light-my-request
#6391
Comments
|
Hey, I'd like to work on this issue. Could you provide some more information? |
|
Hi @rahil1304, thanks for offering your help! What kind of information are you looking for?
As for this issue in particular:
|
|
Unfortunately, we don't have tests for Last but not least, the commit message should annotate the change as breaking, see Making breaking changes in our developer docs. |
|
Also feel free to ask for help in |
|
Hey @bajtos So these are the particular libraries that are being used from @hapi/shot. Just confirming, I need to find the similar libraries that are being used in light-my-way, and accordingly replace it, right? The rest of the code in shot.ts stays the same, right? |
@hapi/shot with light-my-way@hapi/shot with light-my-request
Yes, that's correct. I just realized that the issue title and description were referring to an incorrect module Sorry for the confusion I created AFAICT, |
|
hello, I would love to work on this |
|
@blackpandan sure, please go ahead. |
|
Hi there, if this Issue is still not resolved i would like to give it a shot! |
|
Sure thing, @ConaGo! Feel free to ask queries here or on #loopback-contributors on Slack. The maintainers will try to help where possible. |


Rework
@loopback/testlabto uselight-my-requestfor stubbing HTTP requests & responses.Arguments for the change:
light-my-requesthas larger community of contributors (45 vs 24)light-my-requesthas more activity (compare https://github.com/fastify/light-my-request/graphs/contributors?from=2020-01-01&to=2020-09-18&type=c to https://github.com/hapijs/shot/graphs/contributors?from=2020-01-01&to=2020-09-18&type=c)@hapi/shotdid not support all LTS versions of Node.js, we had to stay at an old major version. Nowadays they don't limit the supported versions viaengines.node, but their CI is configured to test only on Node.js 12+.The text was updated successfully, but these errors were encountered: