Activity

1. gkalpak commented on Nov 5, 2019

   

   gkalpak

   on Nov 5, 2019

   Member

   More actions

   Related PR: #32962

   👍React with 👍4Reacted by Ryan Lester, Vytautas Vaičys, Colin R. Kraebel and Sanju M Mathew
2. AndrewKushnir

   added

   area: coreIssues related to the framework runtimeIssues related to the framework runtime

   on Nov 5, 2019
3. ngbot

   added this to the needsTriage milestone on Nov 5, 2019
4. AndrewKushnir

   added

   featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issues

   on Nov 5, 2019
5. ngbot

   modified the milestones: needsTriage, Backlog on Nov 5, 2019
6. kara

   added

   freq2: medium

   on Nov 5, 2019
7. filipesilva commented on Nov 6, 2019

   

   filipesilva

   on Nov 6, 2019

   Last edited by filipesilva

   Contributor

   More actions

   If you're using the framework/CLI RC and Ivy, you might be able to just use TypeScript 3.7 directly. You'll get a peer dependency warning but in all likelihood it'll just work. Ivy is far less sensitive to TypeScript version changed than View Engine. Let me know if you try this and run into problems.

   Edit: to disable the ERROR in The Angular Compiler requires TypeScript >=3.6.4 and <3.7.0 but 3.7.2 was found instead. error when building, add the angularCompilerOptions.disableTypeScriptVersionCheck option set to true in tsconfig.json:

   {
     // ...
     "angularCompilerOptions": {
       // ...
       "disableTypeScriptVersionCheck": true
     }
   }
   

   👍React with 👍14Reacted by Ryan Lester, Mark, Sean Hale, James Hollowell, Vitaly Tkachenko, x_po, Matthieu Riegler, Grzegorz, Benny Böhm, Abraham Schilling and 4 more

   👀React with 👀2Reacted by Temo Tchanukvadze and Denes Papp
8. gligoran commented on Nov 7, 2019

   

   gligoran

   on Nov 7, 2019

   More actions

   Any possibility this will be ready for the release of Angular 9?

   👍React with 👍7Reacted by Gary Lockett, Asham Sabir, Matt Taube, Damien Daspit, Dave, Denes Papp and Hasan Beheshti

   👀React with 👀4Reacted by Matthias Kunnen, Asham Sabir, Matt Taube and Denes Papp
9. filipesilva commented on Nov 7, 2019

   

   filipesilva

   on Nov 7, 2019

   Contributor

   More actions

   Current thinking at the moment is within version 9, but after 9.0 proper.

   🎉React with 🎉6Reacted by negue, Laurens von Assel, Ryan Lester, Denes Papp, John Hagen and Jay Bishtawi
10. xiaoxiangmoe commented on Nov 7, 2019

    

    xiaoxiangmoe

    on Nov 7, 2019

    More actions

    @filipesilva Will Angular 8 support ts 3.7 in the future?

    👍React with 👍4Reacted by dymo, Martin Iden Leithaug, Sunfung Chang and MagicWang

    👎React with 👎1Reacted by Dave
11. filipesilva commented on Nov 7, 2019

    

    filipesilva

    on Nov 7, 2019

    Contributor

    More actions

    @xiaoxiangmoe I'm not aware of plans to backport the changes needed to version 8. Generally only security fixes and very important bugs are fixed in older versions.

    👍React with 👍1Reacted by Michael Kargl
12. xiaoxiangmoe commented on Nov 22, 2019

    

    xiaoxiangmoe

    on Nov 22, 2019

    More actions

    Can we open useDefineForClassFields in Angular 9? @filipesilva

    👍React with 👍1Reacted by Nicolas HENRY
13. filipesilva commented on Nov 22, 2019

    

    filipesilva

    on Nov 22, 2019

    Contributor

    More actions

    You can try, but that looks like it might cause some trouble... if you run into problems please let us know.
14. alan-agius4 commented on Jan 16, 2020

    

    alan-agius4

    on Jan 16, 2020

    Contributor

    More actions

    Closing as Angular v9.0.0-rc.9 supports TypeScript version 3.7.

    🎉React with 🎉11Reacted by Gustav Bylund, Michael Kriese, LanderBeeuwsaert, Vitaly Tkachenko, Chris Frolik, JSessink, Matt Taube, Frank Mosca, marko164, borismueller and 1 more
15. alan-agius4

    closed this as completedon Jan 16, 2020
16. filipesilva commented on Jan 16, 2020

    

    filipesilva

    on Jan 16, 2020

    Contributor

    More actions

    Support was added in #33717
17. filipesilva commented on Jan 22, 2020

    

    filipesilva

    on Jan 22, 2020

    Last edited by filipesilva

    Contributor

    More actions

    Hey all,

    Starting with @angular/cli@9.0.0-rc.10 and @angular/core@9.0.0-rc.9 you should be able to use TypeScript 3.7 with no problems, while 3.6 is also supported. Please let us know if something if you encounter any problems with the TS version.

    👍React with 👍12Reacted by abagmut, Yann Zahringer Ferrando, Robert Huitl, Sylvain Dumont, Frank Neff, marko164, Vaggal, Mark Chris Levy, Javier Marín, Bram Musters and 2 more

    🎉React with 🎉4Reacted by Marvin Heilemann, marko164, Andrew Rheingans and Bruno Devaux
18. michaeljota commented on Feb 17, 2020

    

    michaeljota

    on Feb 17, 2020

    More actions

    @xiaoxiangmoe Did useDefineForClassFields work for you? I'm seeing a weird issue, and I think it's because of that.
19. michaeljota commented on Feb 17, 2020

    

    michaeljota

    on Feb 17, 2020

    More actions

    I'll try to open another ticket with a reproducible repo but it seems like if you use useDefineForClassFields option will throw somehow if you have a service with a property defined but not initialized.
20. xiaoxiangmoe commented on Feb 17, 2020

    

    xiaoxiangmoe

    on Feb 17, 2020

    More actions

    @michaeljota Sorry, I haven't tried to turn on this option because we are busy with other things.
21. angular-automatic-lock-bot commented on Mar 19, 2020

    

    angular-automatic-lock-botBot

    on Mar 19, 2020

    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.}
22. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Mar 19, 2020