build: remove api-extractor workaround - #43563
Closed
crisbeto wants to merge 1 commit into
Closed
Conversation
crisbeto
marked this pull request as ready for review
September 24, 2021 05:44
Contributor
|
@crisbeto can you please address the conflicts? |
crisbeto
force-pushed
the
api-extractor-workaround
branch
from
September 24, 2021 18:07
e1e5ffb to
39cea2a
Compare
Member
Author
|
Rebased. |
In angular#43281 I had to add a `resolutions`for `typescript` due to the `api-extractor` being locked down to an older version. Now that it has been updated, we don't need the workaround anymore.
crisbeto
force-pushed
the
api-extractor-workaround
branch
from
September 27, 2021 17:53
39cea2a to
719e0d4
Compare
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In #43281 I had to add a
resolutionsfortypescriptdue to theapi-extractorbeing locked down to an older version. Now that it has been updated, we don't need the workaround anymore.