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

Service worker compatibility (fetch vs request) #235

Open
AvivonCtrl opened this issue May 16, 2021 · 3 comments
Open

Service worker compatibility (fetch vs request) #235

AvivonCtrl opened this issue May 16, 2021 · 3 comments

Comments

@AvivonCtrl
Copy link

Hey guys
request-npm is deprecated, mainly because it uses XMLHttpRequest which is no longer supported in Service Workers which is now the background page of Chrome Extensions.

Are there any plans of migrating request to fetch to keep up with JS standards? :)

@jimmywarting
Copy link

Use fetch (and node-fetch) instead of request

@llravelo
Copy link

llravelo commented Apr 8, 2022

Hi guys, do you have any plans to migrate to node-fetch this year?

@apiology
Copy link

apiology commented Nov 5, 2022

I created a little ad-hoc polyfill and substitute it in using yarn config. It seems to work for my needs. Maybe it'll be helpful for others: apiology/upvoter-for-asana@7d4ca40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants