chore: update zshy to 0.8.0 and TypeScript to 6.0.3 - #1370
Open
yagop wants to merge 1 commit into
Open
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.
Upgrade the build toolchain to zshy 0.8.0 and TypeScript 6.0.3. TypeScript 6 rejects the deprecated
baseUrloption in the examples config; remove it and make the existing path mappings relative to that config.Keep TypeScript on 6.x because zshy uses the JavaScript compiler API and the installed TypeDoc version supports TypeScript through 6.0. Consumers can continue using TypeScript 5.
Keep the existing CJS source-map repair step: zshy 0.8.0 still emits ESM map names in CJS output (verified before running postbuild). The upstream fix in colinhacks/zshy#72 is not merged; see issue #71.
npm run checkis cleannpm run buildis cleanValidation
skipLibCheck: false; invalid API parameters are rejected.References