Sitelet https://web.archive.org/web/20211016103650/https://github.com/angular/angular/issues/32380
Skip to content
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

Support TypeScript 3.6 #32380

Closed
EatonZ opened this issue Aug 28, 2019 · 5 comments
Closed

Support TypeScript 3.6 #32380

EatonZ opened this issue Aug 28, 2019 · 5 comments
Milestone

Comments

@EatonZ
Copy link

@EatonZ EatonZ commented Aug 28, 2019

🚀 feature request

Relevant Package

Everything.

Description

TypeScript 3.6 just came out and support should be added.🙂

Describe the solution you'd like

Add support for TypeScript 3.6.
Would be great to see this added for v9 with the Ivy release.

Describe alternatives you've considered

N/A

@sod
Copy link
Contributor

@sod sod commented Sep 13, 2019 •

My guess is, google and their monorepo have the constraint to use the same typescript version across the entire company. And they had some issues going from 3.4 to 3.5 (microsoft/TypeScript#33272). So 3.6 might as well cause issues.

@evmar
Copy link
Contributor

@evmar evmar commented Sep 13, 2019

Probably blocked on angular/tsickle#1065

@EatonZ
Copy link
Author

@EatonZ EatonZ commented Oct 2, 2019

FYI, 3.7 draws near.👀

@lppedd
Copy link

@lppedd lppedd commented Oct 2, 2019 •

@EatonZ I've already compiled with 3.7, seems fine. Actually 3.6 has an issue which makes it incompatible with Angular (using --prod). microsoft/TypeScript#33295

IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 2, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 5, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 5, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 5, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 5, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 10, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 14, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 15, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 16, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 16, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 17, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 17, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 17, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 17, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 17, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
IgorMinar added a commit to IgorMinar/angular that referenced this issue Oct 18, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380
@matsko matsko closed this in 86e1e6c Oct 18, 2019
ODAVING added a commit to ODAVING/angular that referenced this issue Oct 18, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380

PR Close angular#32946
AndrusGerman added a commit to AndrusGerman/angular that referenced this issue Oct 22, 2019
BREAKING CHANGE: typescript 3.4 and 3.5 are no longer supported, please update to typescript 3.6

Fixes angular#32380

PR Close angular#32946
@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Nov 18, 2019

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 Nov 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants