feat(axios-to-whatwg-fetch): introduce #269
Conversation
|
omg please yes |
|
cc @nodejs/userland-migrations can I have first review on this one |
|
It looks like CI did run? If not, was this whilst I was fiddling with the repo permissions? (I specifically told you on slack you'd temporarily have |
it's ran after the merge commit. idk what really happened but it's work now ! it's didn't help since I dunno why windows is doing windows thing |
JakobJingleheimer
left a comment
There was a problem hiding this comment.
Great tidy!
It's still missing handling for transformRequest, transformResponse, paramsSerializer, etc, which was the blocker before. It needs to either
- support them
- detect them and abort/fail the migration
Doing neither will result in broken userland code.
d1ae93f to
469e199
Compare
|
@JakobJingleheimer applied your proposal |
| }, | ||
| }, | ||
| { | ||
| oldBind: '$.request', |
There was a problem hiding this comment.
Ohh 🤦 👍
I think still better to errorWithLocation (because something failed).
axios-to-whatwg-fetch): introduce
Related issue
close #191
info https://socket.dev/blog/axios-npm-package-compromised