Skip to content

polyfills: bundle our own fetch polyfill#647

Merged
saghul merged 1 commit intomasterfrom
refactor-fetch
Sep 3, 2024
Merged

polyfills: bundle our own fetch polyfill#647
saghul merged 1 commit intomasterfrom
refactor-fetch

Conversation

@saghul
Copy link
Copy Markdown
Owner

@saghul saghul commented Aug 21, 2024

It's vendored and slightly adapted whatwg-fetch to start with.

It's vendored and slightly adapted whatwg-fetch to start with.
@saghul saghul marked this pull request as ready for review September 3, 2024 07:47
@saghul
Copy link
Copy Markdown
Owner Author

saghul commented Sep 3, 2024

Alright, here is the plan. This is not fully spec compliant yet, but it is better tailored for our needs since it's easier to modify.

I think the next step would be to create a generic HTTP client which is not XHR or fetch and use it from both directly. This would detach the fetch implementation from XHR and allow us to add the missing stream features. In addition it should simplify the XHR implementation by moving big parts of it to JS. Last, if / when the HTTP library is replaced only one thing needs to be replaced.

@saghul saghul merged commit 5ecea22 into master Sep 3, 2024
@saghul saghul deleted the refactor-fetch branch September 3, 2024 07:50
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

Successfully merging this pull request may close these issues.

1 participant