Update typebox #3532
Closed
Update typebox #3532
+20
−25
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
@sinclair/typebox@^0.25.0 -> ^0.33.9
Member
|
Thank you for the pull request. I branched off of it at #3612 for a working implementation for the next release. |
Member
|
The update to TypeBox version 1 has now been done in #3616 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Tell us about the problem your pull request is solving.
@sinclairzx81/typebox is an awesome project and it is working well with feathers. As there are many new and usable utils like
Type.Compositein newer versions, I usually use to install newer versions to my projects. However, using two different versions creates a lot of problems with type mismatch.The first solution to fix it is to use
resolutionsin the package.json file. but it causes some other problems.Finally, I decided to update it.
Are there any open issues that are related to this?
No!
Is this PR dependent on PRs in other repos?
Only two small changes in @feathers/generators