Repository navigation
build: simplify tooling and contributor workflow - #110
Merged
Merged
Conversation
Merged
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
voischev.ivan@ya.ru, and add contributing/release instructions and a PR template in.github.prepublishOnlybefore publication.Verification
npm ciandnpm run check: build, lint, current/minimum TypeScript checks, tests with coverage and CommonJS/native ESM loading all pass.npm packincludes the expected JavaScript, declarations, source maps, metadata, README and license.npm audit: 0 vulnerabilities.git diff --checkpass.Compatibility
The runtime contract from #109 is preserved: Node.js
^20.19.0 || >=22.12.0, TypeScript 5.3+ consumer declarations, and the synchronous CommonJS/native ESM parser API. Development tools use Node.js 24. The runtime dependency remainshtmlparser2 ^12.0.0; production source files are unchanged.Commit prefixes are documented as optional guidance. CI and pre-publication checks provide automated validation instead of local Git hooks. Release notes are maintained manually, and the documented next parser release is
0.13.0; this PR does not publish a release.