Repository navigation
build: modernize renderer tooling and preserve Node 12 support - #77
Merged
Merged
Conversation
voischev
requested review from
Scrum,
michael-ciniawsky and
mrmlnc
as code owners
October 31, 2026 05:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
tsc, native Node.js tests/assertions, c8 and ESLint.closeAson void tags. Run that suite against isolated production tarball installs on the runtime matrix.This includes and updates the agent workflow guide from #76. Replacing the legacy repository linter also removes the external SchemaStore resolution failure that blocked that PR's CI.
Compatibility
is-json ^2.0.1. The renderer does not load or depend on the parser at runtime, and standalone declaration consumers no longer need parser types installed.Unreleased.Verification
npm ciandnpm run checkpassed on Node.js 24.22.1.npm audit: 0 vulnerabilities (the original installation reported 66).npm pack --ignore-scripts --pack-destination artifactsand tested the same tarball usingnpm run test:packed -- artifacts/posthtml-render-3.0.0.tgz --node <node-executable>on:git diff --checkpassed.CI now checks on Node.js 24, packs the checked build once, then tests that artifact on Node.js 12.0/12/14/16/18/20/22/24/26. npm and TypeScript run on development Node while the full JavaScript suite runs with the selected consumer executable.