locked
Trouble with typescript compilation in Kudu since 2.0 release yesterday. How to change to different typescript version? RRS feed

  • Question

  • Hello,

    I have a couple of ASP.NET web applications hosted in Azure Websites that are deployed via Azure app deployment (connected to bitbucket repositories). These apps have been in Azure for nearly 6 months building without issue, and yesterday afternoon they both started failing with typescript errors.

    After doing some digging on the Kudu scm site, it looks like tpyescript 2.0 was released yesterday and installed on the build server. In folder D:\Program Files (x86)\Microsoft SDKs\TypeScript, I see the following versions installed (and modified dates):

      0.9         9/12/2016, 9:52:43 PM        

      1.0         9/12/2016, 9:52:43 PM        

      1.1         9/12/2016, 9:52:44 PM        

      1.4         9/12/2016, 10:29:14 PM        

      1.5         9/12/2016, 9:52:42 PM        

      1.6         9/12/2016, 10:29:19 PM        

      2.0         10/26/2016, 4:27:31 PM

    Yesterday around 4:30 is precisely when our CI builds started failing. Our csproj files target typescript v1.8 and it seems 2.0 has introduced some changes that break our code.

    My question is - how can I go back to v1.8 on the Kudu server? Do I need to customize the build script somehow to get that version installed?

    Thank you!

    -Zach

    Thursday, October 27, 2016 12:44 PM

Answers

  • Zach, 1.8 is now deployed. Can you give it a try? Thanks!
    • Proposed as answer by David Ebbo Friday, October 28, 2016 10:25 PM
    • Marked as answer by Zach Bussinger Monday, October 31, 2016 12:51 PM
    Friday, October 28, 2016 7:01 PM

All replies

  • Hi Zach,

    Here is my guess as to what happened:

    • Your app targets 1.8
    • We've never had 1.8 (really should but just never did), so the behavior is that you got the latest available, which was 1.6.
    • When we added 2.0 yesterday, that became the latest available and you got that. We did not anticipate that scenario!


    I think we can fix the regression by adding 1.8.

    Until then, another thing you can do is target 1.6 instead of 1.8. Since that's what you were effectively running with before, your code clearly doesn't need anything that's in 1.8 but not 1.6. So I would think that it should work.

    David

    Thursday, October 27, 2016 4:23 PM
  • David,

    Thank you for the reply. Yes, I actually tried this already (updating the csproj to point to 1.6) and it does fix my builds, so I believe your theory is correct! Everything is running smoothly now. And you answered the question that was in my mind, which was "was 1.8 ever installed?"

    If you guys do add 1.8, is there someplace I can watch for these types of updates? Do you notify / publish these types of changes anywhere? I would like to switch our projects back to 1.8 if and when that happens. Thank you,

    -Zach

    Thursday, October 27, 2016 4:28 PM
  • We will try to add 1.8 shortly (next day or two), and will respond on this thread. Then it'd be great if you can confirm that going back to 1.8 works again.

    Sorry for the inconvenience, we really didn't think that adding a new version would break anyone, and obviously we were wrong :(

    David

    Thursday, October 27, 2016 4:33 PM
  • No worries! Kudu has been a fantastic service for us, keep up the good work!
    Thursday, October 27, 2016 4:39 PM
  • Zach, 1.8 is now deployed. Can you give it a try? Thanks!
    • Proposed as answer by David Ebbo Friday, October 28, 2016 10:25 PM
    • Marked as answer by Zach Bussinger Monday, October 31, 2016 12:51 PM
    Friday, October 28, 2016 7:01 PM
  • All looks good now, targeting 1.8 in our csproj file. Thanks for the follow up!
    Friday, October 28, 2016 10:16 PM
  • Awesome!
    Friday, October 28, 2016 10:25 PM