Skip to content

refactor: Update API usage of sax-wasm#567

Draft
matz3 wants to merge 1 commit intomainfrom
update-sax-wasm-usage
Draft

refactor: Update API usage of sax-wasm#567
matz3 wants to merge 1 commit intomainfrom
update-sax-wasm-usage

Conversation

@matz3
Copy link
Copy Markdown
Member

@matz3 matz3 commented Feb 25, 2025

  • Updating to the new recommended API of sax-wasm
  • Reuse parseXML in xml transpiler
@matz3 matz3 requested a review from a team February 25, 2025 10:14
parseHandler(event, detail);
}

await finished(contentStream);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is finished still required? I would expect that the iterator is exhaustive? The sax-wasm README does not call finished in the ReadableStream example...

BTW: toWeb is still experimental in Node 23 (according to their docs)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I guess not but I thought it shouldn't hurt leaving it there. But good point about the experimental API. Then we shouldn't use it, yet.

@matz3 matz3 marked this pull request as draft February 25, 2025 14:14
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jun 23, 2025

CLA assistant check
All committers have signed the CLA.

Updating to the new recommended API of sax-wasm.
This also prevents TypeScript 5.9 errors caused by the used node types
which are pinned to the minimum supported version of Node.js.
@matz3 matz3 force-pushed the update-sax-wasm-usage branch from e4bc823 to 1f84f7c Compare August 5, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants