Repository navigation
Fix documentation build and validate it in CI - #21
Merged
Merged
Conversation
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.
Description
yarn docsfails with TS2774 in the secure-random helper. Use an explicit function capability check and pin TypeScript 5.1.6, which is supported by both TypeDoc 0.27 and the existing ESLint parser.Build documentation in pull-request CI so this failure cannot pass unnoticed. Use frozen installs in CI and Read the Docs, and complete missing lockfile entries for existing build dependencies.
Validation: documentation generated successfully (21 non-blocking documentation warnings remain); all 58 test suites / 718 tests passed, including browser and Node initialization; targeted ESLint and frozen offline install passed.
Checklist