build: remove ng-dev typescript configuration workaround #19415
Merged
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
We recently added a workaround to support having a `ng-dev` configuration written in TypeScript. The `ng-dev` tool now automatically sets up `ts-node` when needed, so we can remove the workaround. Additionally, we can replace the merge branch determining logic as the script has been moved upstream. It has been also improved to no longer rely on Git but rather on the NPM registry.
googlebot
added
the
cla: yes
devversion
added
merge safe
target: major
|
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. |
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.
We recently added a workaround to support having a
ng-devconfiguration written in TypeScript. The
ng-devtool nowautomatically sets up
ts-nodewhen needed, so we can removethe workaround.
Additionally, we can replace the merge branch determining logic
as the script has been moved upstream. It has been also improved
to no longer rely on Git but rather on the NPM registry.