mholt/PapaParse

Upgrade XHR to use the fetch API

Open

#182 opened on Mar 13, 2015

View on GitHub
 (4 comments) (2 reactions) (0 assignees)JavaScript (11,877 stars) (1,157 forks)batch import
help wantedsuggestion

Description

The next versions of Chrome, Opera, and Firefox will support fetch. It would be nice to phase out XHR and push the newer technologies.

Fetch isn't completed yet but when it is more stable and widely adopted, this would be great. Here's more info: http://jakearchibald.com/2015/thats-so-fetch/

(This issue is more of a memo to self. But comments/questions are welcome too.)

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptXHR knowledgefetch API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue proposes replacing XHR with the fetch API in PapaParse's CSV parsing. First, identify all places where XHR is used in the codebase, likely in the file(s) handling HTTP requests (e.g., PapaParse.js). Then, implement a fetch based alternative while preserving backward compatibility for older browsers, possibly using a polyfill. Consider the existing comments; discussion indicates fetch was not stable at the time, but now it is widely supported.