Skip to content

imscJS 2.0-dev.1 - #268

Merged
palemieux merged 21 commits into
mainfrom
integration/v2
Sep 1, 2026
Merged

imscJS 2.0-dev.1#268
palemieux merged 21 commits into
mainfrom
integration/v2

Conversation

@palemieux

@palemieux palemieux commented Sep 1, 2026

Copy link
Copy Markdown
Contributor
  • move to ES6 modules
  • adds linting
  • move to modern JS packager
  • parameterizes the XML parser, allowing the use of the native browser DOMParser

Closes #242

littlespex and others added 19 commits April 26, 2024 15:13
- replace jshint with eslint
- replace closure compiler with rollup + terser
- replace browserify with rollup + tsc
Co-authored-by: Pierre-Anthony Lemieux <pal@sandflow.com>
Co-authored-by: Pierre-Anthony Lemieux <pal@sandflow.com>
Co-authored-by: Pierre-Anthony Lemieux <pal@sandflow.com>
- sax 1.2.1 -> ^1.6.1: hardening against hostile input (quadratic
  CDATA allocation fix, attribute count/depth limits, invalid code
  point checks, stricter char-ref validation in strict mode).
  Note: sax relicensed ISC -> BlueOak-1.0.0 as of 1.4.2.
- @rollup/plugin-commonjs ^29, @rollup/plugin-node-resolve ^16,
  globals ^17: major bumps, no config changes required.
- eslint / @eslint/js floors raised to current 9.x.
- Lockfile regenerated; npm audit reports 0 vulnerabilities.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…owser DOMParser

Closes #242

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Pierre-Anthony Lemieux <pal@sandflow.com>
@palemieux

Copy link
Copy Markdown
Contributor Author

@littlespex Ready to switch the master branch to this branch?

@littlespex

littlespex commented Sep 1, 2026

Copy link
Copy Markdown

What is plan for the Headless generation of reference renders, and possibly chore: replace grunt with npm scripts PRs? Should they be merged into integration/v2 before this PR is merged, or into main after?

@palemieux

Copy link
Copy Markdown
Contributor Author

What is plan for the Headless generation of reference renders, and possibly chore: replace grunt with npm scripts PRs? Should they be merged into integration/v2 before this PR is merged, or into main after?

I think we should consider them after the merge.

I have just added #269 which addresses a fatal bug.

I am not super convinced (yet) with jettisoning grunt given the alternative is pretty wordy and grunt has worked well for us.

@littlespex

Copy link
Copy Markdown

Understood. I think this is good to go.

littlespex and others added 2 commits September 1, 2026 09:07
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@palemieux
palemieux changed the base branch from master to main September 1, 2026 16:16
@palemieux
palemieux merged commit dac54ce into main Sep 1, 2026
1 check passed
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.

Replace the XML SAX parser with a DOM parser

2 participants