-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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
feat: add support for typescript 3.2 #27536
Conversation
0f86dfc
to
3ff3b65
Compare
You can preview 0f86dfc at https://pr27536-0f86dfc.ngbuilds.io/. |
You can preview 3ff3b65 at https://pr27536-3ff3b65.ngbuilds.io/. |
3ff3b65
to
42d7176
Compare
You can preview 42d7176 at https://pr27536-42d7176.ngbuilds.io/. |
42d7176
to
8d4ba41
Compare
You can preview 8d4ba41 at https://pr27536-8d4ba41.ngbuilds.io/. |
You can preview d784ba0 at https://pr27536-d784ba0.ngbuilds.io/. |
d784ba0
to
ff0edd5
Compare
You can preview ff0edd5 at https://pr27536-ff0edd5.ngbuilds.io/. |
ff0edd5
to
f5a6d4c
Compare
You can preview f5a6d4c at https://pr27536-f5a6d4c.ngbuilds.io/. |
f5a6d4c
to
1530a94
Compare
You can preview 1530a94 at https://pr27536-1530a94.ngbuilds.io/. |
You can preview d8202f3 at https://pr27536-d8202f3.ngbuilds.io/. |
@@ -8,6 +8,8 @@ | |||
import {dirname} from 'canonical-path'; | |||
import {existsSync, writeFileSync} from 'fs'; | |||
import {mkdir, mv} from 'shelljs'; | |||
// "unused" import needed by tsc type inference | |||
import * as ts from 'typescript'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is required by the return type of Transformer.analyzeProgram
being inferred (and the inferred type including TS types). If you make that return type explicit, this statement won't appear unused.
d8202f3
to
a6e6763
Compare
You can preview a6e6763 at https://pr27536-a6e6763.ngbuilds.io/. |
You can preview 00e0894 at https://pr27536-00e0894.ngbuilds.io/. |
import { createCustomElement } from '@angular/elements'; | ||
|
||
// huh? not sure why, but ts 3.2 emits broken code for: `import { from as fromPromise, ...} from 'rxjs'; | ||
// this const alias works around the problem. | ||
const fromPromise = from; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not update the references to not use the alias?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's what I'll do for now, I just wanted to get more people to take a look at this because import as
should work and shouldn't break with a typescript update.
I filed angular/angular-cli#13212 to track this.
caretaker note: pullapprove and travis flaked |
…al (#27536) Typescript 3.2 introduced BigInt type, and consequently the implementation for checkExpressionWorker() in checkers.ts is refactored. For NumberLiteral and StringLiteral types, 'text' filed must be present in the Node type, therefore they must be LiteralLikeNode instead of Node. PR Close #27536
It's unclear why `import as` results in the aliases to be undefined. Plain tsc seems to do the right thing and emits the correct code, so it might be some kind of interaction in @angular/cli or webpack that are causing the failure. This should be investigated separately from the tsc update in angular/angular. See angular/angular-cli#13212 PR Close #27536
…mpilerOptions (#27536) We need to do this because we don't yet have a released version of angular with typescript 3.2 support and on CI we test both against the snapshot and whatever is in aio/yarn.lock. Once we have the next rc or a stable relase we should be able to remove this flag. PS: I also removed the preserveWhitespace:false because that's the default now. PR Close #27536
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/ Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34 PR Close angular#27536
…al (angular#27536) Typescript 3.2 introduced BigInt type, and consequently the implementation for checkExpressionWorker() in checkers.ts is refactored. For NumberLiteral and StringLiteral types, 'text' filed must be present in the Node type, therefore they must be LiteralLikeNode instead of Node. PR Close angular#27536
It's unclear why `import as` results in the aliases to be undefined. Plain tsc seems to do the right thing and emits the correct code, so it might be some kind of interaction in @angular/cli or webpack that are causing the failure. This should be investigated separately from the tsc update in angular/angular. See angular/angular-cli#13212 PR Close angular#27536
…ngular#27536) cli is not yet officially compatible with typescript 3.2, so we need to disable the version check via: ng config cli.warnings.typescriptMismatch false PR Close angular#27536
…mpilerOptions (angular#27536) We need to do this because we don't yet have a released version of angular with typescript 3.2 support and on CI we test both against the snapshot and whatever is in aio/yarn.lock. Once we have the next rc or a stable relase we should be able to remove this flag. PS: I also removed the preserveWhitespace:false because that's the default now. PR Close angular#27536
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/ Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34 PR Close angular#27536
…al (angular#27536) Typescript 3.2 introduced BigInt type, and consequently the implementation for checkExpressionWorker() in checkers.ts is refactored. For NumberLiteral and StringLiteral types, 'text' filed must be present in the Node type, therefore they must be LiteralLikeNode instead of Node. PR Close angular#27536
It's unclear why `import as` results in the aliases to be undefined. Plain tsc seems to do the right thing and emits the correct code, so it might be some kind of interaction in @angular/cli or webpack that are causing the failure. This should be investigated separately from the tsc update in angular/angular. See angular/angular-cli#13212 PR Close angular#27536
…ngular#27536) cli is not yet officially compatible with typescript 3.2, so we need to disable the version check via: ng config cli.warnings.typescriptMismatch false PR Close angular#27536
…mpilerOptions (angular#27536) We need to do this because we don't yet have a released version of angular with typescript 3.2 support and on CI we test both against the snapshot and whatever is in aio/yarn.lock. Once we have the next rc or a stable relase we should be able to remove this flag. PS: I also removed the preserveWhitespace:false because that's the default now. PR Close angular#27536
Package "ng-zorro-antd" has an incompatible peer dependency to "typescript" (requires "~3.1.1", would install "3.2.2"). I can not update ngrx to 7.0.0, please help, when can support typescript 3.2? |
angular framework 7.2 has been released on Monday with typescript 3.2
support:
https://github.com/angular/angular/blob/master/CHANGELOG.md#720-2019-01-07
…On Tue, Jan 8, 2019 at 7:43 PM zw ***@***.***> wrote:
Package "ng-zorro-antd" has an incompatible peer dependency to
"typescript" (requires "~3.1.1", would install "3.2.2").
I can not update ngrx to 7.0.0, please help, when can support typescript
3.2?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27536 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANM6Ml2VMukiLU4yMdn32KtZ867HHlhks5vBWVPgaJpZM4ZH6Eb>
.
|
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/ Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34 PR Close angular#27536
…al (angular#27536) Typescript 3.2 introduced BigInt type, and consequently the implementation for checkExpressionWorker() in checkers.ts is refactored. For NumberLiteral and StringLiteral types, 'text' filed must be present in the Node type, therefore they must be LiteralLikeNode instead of Node. PR Close angular#27536
It's unclear why `import as` results in the aliases to be undefined. Plain tsc seems to do the right thing and emits the correct code, so it might be some kind of interaction in @angular/cli or webpack that are causing the failure. This should be investigated separately from the tsc update in angular/angular. See angular/angular-cli#13212 PR Close angular#27536
…ngular#27536) cli is not yet officially compatible with typescript 3.2, so we need to disable the version check via: ng config cli.warnings.typescriptMismatch false PR Close angular#27536
…mpilerOptions (angular#27536) We need to do this because we don't yet have a released version of angular with typescript 3.2 support and on CI we test both against the snapshot and whatever is in aio/yarn.lock. Once we have the next rc or a stable relase we should be able to remove this flag. PS: I also removed the preserveWhitespace:false because that's the default now. PR Close angular#27536
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. |
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html
https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/
Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34