Skip to content

build: vendor typescript 3.6 in build optimizer #17670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 11, 2020
Merged

build: vendor typescript 3.6 in build optimizer #17670

merged 3 commits into from
May 11, 2020

Conversation

alan-agius4
Copy link
Collaborator

With this change we "vendor" TypeScript 3.6 in build optimizer instead of using directly the npm package.

Reasons:

@alan-agius4 alan-agius4 added the target: major This PR is targeted for the next major release label May 8, 2020
@alan-agius4 alan-agius4 requested a review from filipesilva May 8, 2020 11:47
With this change we "vendor" TypeScript 3.6 in build optimizer instead of using directly the npm package.

Reasons:
- We cannot update to a more recent version of TypeScript due to microsoft/TypeScript#38412
- Yarn workspace are not supported under Bazel. This means currently we are running unit testswhich uses a different TypeScript version at runtime.
- In TypeScript 3.9, the shape of ES2015 classes changed microsoft/TypeScript#32011, this requires some changes in the UT expects, but this again will not be correct to change now.
Since we are importing the vendored typescript with relative imports, module_name and module_root in the its ts_library are not needed.

See: #17670 (comment) for more context
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label May 9, 2020
@clydin clydin merged commit 1227a2c into angular:master May 11, 2020
@alan-agius4 alan-agius4 deleted the build-optimizer-ts-3.6 branch May 11, 2020 12:08
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants