fix(compat): update patch for [email protected]
#5296
Merged
Conversation
This file contains 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
merceyz
added a commit
that referenced
this pull request
Mar 4, 2023
* fix(compat): update patch for `[email protected]` * chore: [email protected]
|
@merceyz Is there any plan to port this patch back to v3 release? |
|
I've already backported it, it's the commit you can see above your comment, and prepared the next release, it's waiting on @arcanis to have time to create the release. |
|
@arcanis TS 5 will be released at 3/16 (very soon). Good to see if it works with Yarn 3. |
|
TS 5 has been released. microsoft/TypeScript#51362 (comment) |
|
Yarn v3.5.0 has been released yarn set version berry |
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.
What's the problem this PR addresses?
The PnP compatibility patch for TypeScript doesn't apply to
[email protected].Ref microsoft/TypeScript#35206
How did you fix it?
Rebased #5210 onto the
5.0.1-rcrelease.Checklist