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

Broken in Node18? #189

Open
joebowbeer opened this issue Apr 20, 2023 · 0 comments
Open

Broken in Node18? #189

joebowbeer opened this issue Apr 20, 2023 · 0 comments

Comments

@joebowbeer
Copy link
Contributor

joebowbeer commented Apr 20, 2023

I am almost certain that the use of cross-fetch/polyfill will not replace the new experimental global fetch introduced in Node18.

This can result in unintended consequences in some edge cases:

lquixada/cross-fetch#155
node-fetch/node-fetch#1566

For example, I suspect some tls options may not be supported:

https://stackoverflow.com/q/73817412/901597

Workaround: Explicitly disable native fetch via --no-experimental-fetch

@joebowbeer joebowbeer changed the title cross-fetch/polyfill may not work as expected in Node18? Broken in Node18? Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant