fix: resolve peer dependency conflicts#77
Merged
Conversation
- Downgrade marked ^18.0.5 -> ^15.0.0 to satisfy marked-terminal@7.3.0 peer dependency (requires marked <16) - Downgrade typescript ^6.0.3 -> ^5.9.3 to satisfy openapi-typescript@7.13.0 peer dependency (requires ^5.x) Fixes npm ERESOLVE warnings and npm ls 'invalid' flags on clean install.
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.
Problem
Installing the CLI produces npm peer dependency warnings:
marked-terminal@7.3.0requiresmarked@<16, butpackage.jsonspecifiedmarked@^18.0.5openapi-typescript@7.13.0requirestypescript@^5.x, butpackage.jsonspecifiedtypescript@^6.0.3This caused
npm installto emit ERESOLVE warnings andnpm lsto flag packages asinvalid.Changes
marked^18.0.5^15.0.0marked-terminalpeer dep requires<16(upstream issue)typescript^6.0.3^5.9.3openapi-typescriptpeer dep requires^5.x(upstream PR pending release)Verification
npm install— zero warningsnpm ls --all— noinvalid,unmet,missing, orextraneousflagsnpm audit— 0 vulnerabilitiesnpm run build— passesnpm run test:run— 283 tests pass