[WIP] Replace sax with saxes #1127
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
THIS PR IS NOT READY TO BE MERGED - IT IS A PoC
As mentioned last year (#748 (comment)), I believe we should consider replacing
sax
withsaxes
. Here are my main motivating reasons:sax
has not been maitained in close to 3 yearssaxes
uses ES6 and modern streams, which should enable us to use async iterators, which a) massively simplifies the code responsible for the stream control logic and b) handles backpressure for us, which could mean we might be able to drop our custom flow control implementationsaxes
is faster thansax
This PR is a work in progress right now and cannot be merged until
saxes
v5 is officially released. It also requires that we replace uglify with terser to handle the ES6 code thatsaxes
publishes.Looking forward to your feedback!