First coding week

6 min read- views

The first week working on the migration of Jangouts to Angular2.

The first week of the coding period at GSoC 2016, so I started the upgrading process of Jangouts from Angular 1.x to Angular 2. This week, the tasks have been fulfilled within the deadline, I hope to remain so for the next week.

I'm following the upgrade guide from official Angular docs, which has two main blocks:

  • Preparation
  • Upgrading with The Upgrade Adapter

I just finished the preparation block. I was lucky because the code of Jangouts is really clear and it follows two important points of the preparation block: Follow the Angular style guide and use component directives. So this left me only two things to do. First of all, switch from load files with <script> tags to a module loader and then migrate the code from JavaScript to TypeScript. But I've done it in reverse order, first migrate to TypeScript and then switch to a module loader. Why? I think this way is more "natural", at least for this project.

Migrating to TypeScript

Jangouts has a gulp build system working, so I didn't have to worry about how the scripts are loaded. First I worry about migrating the files to TypeScript and when all was ready, then I try to take profit from the import syntax of TypeScript/ES6.

Migrate code from JavaScript to TypeScript is really easy, only need to change the extension form .js to .ts. Obviously, the existing gulp system doesn't works with these changes, so in parallel of running gulp you should run tsc --watch src/**/*.ts. This command shows a lot of errors but don't worry about this if the JavaScript code is correct, all these errors are related to the type checking process of TypeScript compiler.

During this migration process, I also perform some changes in the code to make it more modular. Jangouts have all the components registered in the same Angular module janusHangouts and in other projects I worked before I learned that this can make some troubles when you have to do unit testing, so I define a different module for each component (janusHangouts.componentName) and then make it a dependency of the main module. This has to advantages: make tests is easier and in the future we can load components on demand with a module loader (but I'm not sure about the last one).

Back to some, I said earlier, when compiling the JavaScript code with tsc this shows a lot of errors. One that could appear a lot is something like this:

error TS7006: Parameter '$state' implicitly has an 'any' type.

This is because TypeScript compiler wants a type defined for all variables, but we can make that tsc set the implicit type any for variables without type. The only thing to do is disable the option noImplicitAny in the tsconfig.json file.

Another error we can find when working with HTML elements is:

error TS2339: Property 'muted' does not exist on type 'HTMLElement'.

This error is produced from a code like that:

var video = $('video', element)[0];
video.muted = true;

The error is produced because TypeScript is type save. So the $('video', element)[0] returns the type HTMLElement which does not contain a muted property. The subtype HTMLVideoElement does however contain the muted property. So the solution is to cast the result to HTMLVideoElement like this:

var video = <HTMLVideoElement>$('video', element)[0];
video.muted = true;

Finally, another common error is:

error TS2339: Property 'id' does not exist on type '{}'.

This is another "problem" produced by the type validations of TypeScript. We can found errors like that in fragments of code similar to:

var room = {};
// Some code here...
function isRoom(room) {
return == roomId;

To solve this and make the code less error-prone, we should define an interface for the room object.

interface Room {
id?: number; // ? makes the attribute optional
// Some code here ...
var room: Room = {};
// Some code here...
function isRoom(room: Room) {
return == roomId;

Using a Module Loader

Why we should use a module loader? We can find the response in Angular site:

Using a module loader such as SystemJS, Webpack, or Browserify allows us to use the built-in module systems of the TypeScript or ES2015 languages in our apps. We can use the import and export features that explicitly specify what code can and will be shared between different parts of the application. [...]

When we then take our applications into production, module loaders also make it easier to package them all up into production bundles with batteries included.

I discard Browserify because I had bad experiences in the past. So I have only tried with SystemJS and Webpack.


SystemJS looks really clean, really simple. The only thing I was to do is define an entry point (normally the main file of the application) and the import syntax do the rest. So, if we have the import statements correctly placed, all work without a problem.

But with this solution, we need to conserve gulp, because SystemJS only cares about the imports. So this implies add the TypesScript compiler to gulp and disable the auto inject of script in html.

Sincerely I didn't try that before trying to rewrite the gulp configuration I wanted to have a look at Webpack first.


The configuration of Webpack is more complex than SystemJS, but it gives a substitution of gulp. As SystemJS does, we need to define an entry point for the application and also tell him where is the index.html to include the JavaScript files.

Initially, I had some troubles, but after looking at some examples, I had a functional version. Exploring more depth in Webpack I found something that makes me choose it before others: we can import or require non JavaScript files. So we can do things like require the template of an Angular directive, and in the building process this template will be included as a string variable inside the component, and with styles we have the same feature. This functionality improves the final build of the application because all the files needed by a component will be placed inside the JavaScript file of the component, improving the performance but without making difficult program it.

One more thing

This summer looks exciting with all the things I have to learn with GSoC. If you want to follow the progress of what I'm doing keep update of this blog or follow my contributions on GitHub. Also, I published a Trello board with the planning and things to do with this project (not fully update yet but in progress).