GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add support for TypeScript 2.8 · Issue #23779 · angular/angular

Add support for TypeScript 2.8 #23779

New issue
Copy link
New issue
Copy link
Closed
Closed
Add support for TypeScript 2.8#23779
Copy link
Assignees
LucasSloan
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimefeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfreq3: high
Milestone
Backlog

Description

@IgorMinar
IgorMinar
opened on May 8, 2018
Issue body actions

Typescript 2.8 info:

  • https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-8.html
  • https://blogs.msdn.microsoft.com/typescript/2018/03/27/announcing-typescript-2-8/

Typically a TypeScript update means the following things:

  • ensure that tsickle is compatible with the new version of typescript
  • ensure that rxjs is compatbile
  • update our main package.json and yarn.lock to reflect the typescript 2.8 dependency
  • add a new test for ts28 similar to https://github.com/angular/angular/tree/77ff72f93b86e57ba3fdc67a60a5b00c69c9a824/integration/typings_test_ts27
  • ensure that our codebase can compile with typescript 2.8. Usually the tighter compiler checks surface preexisting errors that we need to fix in a way that
    • doesn't change our public api
    • doesn't make our published d.ts files incompatible with typescript 2.7
  • ensure that our code that users TS AST and compiler apis are compatible (primarily compiler-cli and language-service) - if we need to make any updates we need to make sure that we remain both 2.7 and 2.8 compatible.
  • point out anything Angular-specific and noteworthy that we need to let Angular developers know when they update to 2.8 (new flags, etc)

Previous PR with 2.7 update just for reference: #22669

Reacted by Bnaya Peretz, Suguru Inatomi, Jan Melcher, Rodrigo Alves, Olaf Kasper, juergenr, Kenji Imamula, Quentin, Marvin Heilemann, rafaelfgx and 33 more
Reacted by Alan Agius, Alex Sharov, David J. M. Karlsen, Maxence Frenette, Michael Kriese, Emanuel Dejanu and Jim Rasche

Activity

Next
  1. IgorMinar
    assigned
    LucasSloan
    on May 8, 2018
  2. IgorMinar commented on May 8, 2018

    @IgorMinar
    IgorMinar
    on May 8, 2018
    ContributorAuthor
    More actions

    @LucasSloan has offered to take this one on, @alxhub can you please help with code reviews? thanks!

    Reacted by Paulo Otavio Gomes de Abreu Pinto
  3. LucasSloan commented on May 8, 2018

    @LucasSloan
    LucasSloan
    on May 8, 2018
    Contributor
    More actions

    There was a previous issue #23092, could you merge or link or whatever?

  4. IgorMinar commented on May 8, 2018

    @IgorMinar
    IgorMinar
    on May 8, 2018 via email
    ContributorAuthor
    More actions
    Bah! I knew there was an issue for this already but search couldn't find it. I deduped the issues. Thanks
    …
    On Tue, May 8, 2018, 1:52 PM Lucas Sloan ***@***.***> wrote: There was a previous issue #23092 <#23092>, could you merge or link or whatever? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23779 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANM6ElRgwEDtdEiI529_9om2esiJjEhks5twgWJgaJpZM4T3UCB> .
  5. mhevery
    added
    area: coreIssues related to the framework runtimeIssues related to the framework runtime
    on May 8, 2018
  6. ngbot
    added this to the needsTriage milestone on May 8, 2018
  7. mhevery
    added
    freq3: high
    severity2: inconvenient
    featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issues
    on May 10, 2018
  8. ngbot
    modified the milestones: needsTriage, Backlog on May 10, 2018
  9. MrWolfZ commented on Jun 24, 2018

    @MrWolfZ
    MrWolfZ
    on Jun 24, 2018
    More actions

    Is someone still working on this? Or are you looking for contributors?

  10. sarunint commented on Jun 24, 2018

    @sarunint
    sarunint
    on Jun 24, 2018
    Contributor
    More actions

    @MrWolfZ It has been done in #23782 and is scheduled for v6.1.

  11. alan-agius4 commented on Jun 24, 2018

    @alan-agius4
    alan-agius4
    on Jun 24, 2018 via email
    Contributor
    More actions
    This is already been done in master branch ie for v6.1.X #23782
    …
    On Sun, 24 Jun 2018 at 18:40, Jonathan Ziller ***@***.***> wrote: Is someone still working on this? Or are you looking for contributors? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#23779 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQv-Wp8Tz9caHRIjxh4uviHa0Z9LubXfks5t_8ETgaJpZM4T3UCB> .
  12. 1 remaining item

  13. trotyl commented on Jun 25, 2018

    @trotyl
    trotyl
    on Jun 25, 2018
    Contributor
    More actions

    But this is a checklist, one can found which parts have already been done.

    The ensure that our codebase can compile with typescript 2.8. item mentioned above has been checked already.

  14. gkalpak commented on Jun 25, 2018

    @gkalpak
    gkalpak
    on Jun 25, 2018
    Member
    More actions

    Is there anything left to do here, @IgorMinar?
    The only remaining item is:

    point out anything Angular-specific and noteworthy that we need to let Angular developers know when they update to 2.8 (new flags, etc)

  15. ericmartinezr commented on Jun 25, 2018

    @ericmartinezr
    ericmartinezr
    on Jun 25, 2018
    Contributor
    More actions

    Shouldn't this one be superseded by #24652 ?

    Reacted by Martin Boekhoff, Dave, Xceno and Terry
  16. insidewhy commented on Jun 26, 2018

    @insidewhy
    insidewhy
    on Jun 26, 2018
    More actions

    When installing the 6.1.0-beta.2:

    warning "@angular-devkit/build-angular > @ngtools/[email protected]" has incorrect peer dependency "typescript@~2.4.0 || ~2.5.0 || ~2.6.0 || ~2.7.0".
    

    Can I ignore this warning or is typescript 2.8 not available in the released version? If not, do you know which version of angular ts 2.8 will be supported from?

  17. vladimiry commented on Jun 26, 2018

    @vladimiry
    vladimiry
    on Jun 26, 2018
    More actions

    @ohjames try to put disableTypeScriptVersionCheck option into your tsconfig.json

      "angularCompilerOptions": {
        "disableTypeScriptVersionCheck": true
      }
    Reacted by Manuel Lopez and Nikolai Orekhov
    Reacted by rujorgensen
  18. insidewhy commented on Jun 26, 2018

    @insidewhy
    insidewhy
    on Jun 26, 2018
    More actions

    @vladimiry I don't think that's even needed, it's just a warning from yarn/npm about peer dependency being violated. I can ignore it but I'm not sure if ts 2.8 is supported by the current 6.1 beta (mostly due to this peer dependency).

  19. vladimiry commented on Jun 26, 2018

    @vladimiry
    vladimiry
    on Jun 26, 2018
    More actions

    but I'm not sure if ts 2.8 is supported by the current 6.1 beta

    IMHO, you can't know that for sure until it's officially stated by Angular team.

    Btw I go with latest TS and Angular versions and usually it works well, like now using TS 2.9.2 and Angular 6.0.6, have not tried beta though.

    Can I ignore this warning

    This doesn't look like a warning to me

    angular/packages/compiler-cli/src/transformers/program.ts

    Line 926 in c95437f

    throw new Error(

    @ohjames Ah, sorry, I overlooked your original message, in your case it's about a dependency warnings shown by npm/yarn.

  20. zuozhiw commented on Jul 3, 2018

    @zuozhiw
    zuozhiw
    on Jul 3, 2018
    More actions

    @vladimiry I'm struggling to combine the latest version of typescript (TS 2.9.2 currently) and the latest Angular version (it needs TS 2.7.2). I did what you said: disableTypeScriptVersionCheck in tsconfig.json, and I also disabled the typescriptMismatch warning in Angular CLI.

    However, when I do ng serve, I get this error ERROR in The Angular Compiler requires TypeScript >=2.7.2 and <2.8.0 but 2.9.2 was found instead.It seems like I need to install the peer dependency for Angular compiler on my own. Could you please guide me on how to do this, or point me to some online resources? Thanks

  21. vladimiry commented on Jul 3, 2018

    @vladimiry
    vladimiry
    on Jul 3, 2018
    More actions

    @zuozhiw I don't use CLI, but use compiler directly in Webpack config. Based on the information you provided it looks like angularCompilerOptions.disableTypeScriptVersionCheck option didn't take an affect. I'd suggest to double check that you changed a right tsconfig.json file. You can also debug it (at least using console.log approach), see related code line in my previous comment.

  22. albyrock87 commented on Jul 6, 2018

    @albyrock87
    albyrock87
    on Jul 6, 2018
    More actions

    @zuozhiw That option goes into tsconfig.app.json .. The "angularCompilerOptions" section is already there!

  23. gkalpak commented on Jul 26, 2018

    @gkalpak
    gkalpak
    on Jul 26, 2018
    Member
    More actions

    I am closing this, since it seems to be complete. (@IgorMinar, reopen if not.)
    There is a separate issue for tracking problems with TS 2.9: #25141

  24. gkalpak
    closed this as completedon Jul 26, 2018
  25. angular-automatic-lock-bot commented on Sep 13, 2019

    @angular-automatic-lock-bot
    angular-automatic-lock-botBot
    on Sep 13, 2019
    More actions

    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.

  26. angular-automatic-lock-bot
    locked and limited conversation to collaborators on Sep 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @LucasSloan
    LucasSloan

Labels

area: coreIssues related to the framework runtimeIssues related to the framework runtimefeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfreq3: high

Type

No type

Projects

No projects

    Milestone

    • BacklogNo due date

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.