… And then you’re done: now your ES6 TypeScript packages should compile without issues.
![how to repair visual studio 2015 update 3 how to repair visual studio 2015 update 3](https://allpcworld.com/wp-content/uploads/2016/10/Visual-Studio-Professional-2015-Update-3-Review.jpg)
The easiest workaround is to simply switch the transpiler’s target from ES5 to ES6. The following workarounds have been tested against Angular2 RC1 through RC4, thus they should also work for any other similar packages affected with the same issue. When we’re hitting these scenarios, we need to manually guide the transpiler to the typings. Index.d.ts file in each package root folder: most of the times, that’s enough to find what’s needed to compile the scripts: however, it can happen that one or more alpha, beta and/or RC library packages we’ve been using could be missing some typings, or even the whole typings (or typings reference) file. Back to the topic, it’s worth noticing that the TypeScript compiler does what it can to automatically find the typings by looking for a If you want to read more about them, I suggest you to read the relevant chapter from the official TypeScript documentation. Typings, or Type Definitions, are what the TypeScript transpiler needs to properly resolve Node module names by following the Node.js module resolution algorithm.
![how to repair visual studio 2015 update 3 how to repair visual studio 2015 update 3](https://i.stack.imgur.com/XR1W7.jpg)
You might now ask: “what does making the transpiler aware exactly means?” Well, that’s a good question. That’s certainly the case of Angular2 RC1 to RC4, which happened to be my specific scenario, but the exact same thing will most likely happen with a number of other modern TS-based libraries. Long story short, the issue seems to happen when you’re dealing with TypeScript files using ES6 methods without making the transpiler aware about them. Since I feel like it can happen to other developers, I will share the workarounds I found hoping to help someone to waste less time than I had to. I managed to fix that, but it took a fair amount of time due to the lack of documentation almost anywhere.
HOW TO REPAIR VISUAL STUDIO 2015 UPDATE 3 UPGRADE
Īs far as I knew, the issue was indeed related to the recent upgrade I made switching Angular2 beta to Angular2 RC1.
![how to repair visual studio 2015 update 3 how to repair visual studio 2015 update 3](https://lh3.googleusercontent.com/-gD3AgBVKAPU/V3Kj-mEYSfI/AAAAAAAARRE/M4zd08uDFOM/header%255B2%255D.png)