Ng2Emulation – TypeScript Angular 1.4+ code using Angular 2 style

Puedes leer este post en español aquí.

I have doing “a thing” 😀 that I called Ng2Emulation, I’m going to try explain it.

Background history

After two days with Angular 2 I’m going understand it and I like it.

I’m envolved in the development of a custom ERP (propietary) and I have to start develop the new user interface for our ERP. The ERP has 8 years old and, seems, it will have a long live. I have decided to build this UI using Angular and TypeScript. Due to project will be a long time I need prepare for future changes, I would like use Angular 2 when it is available but I know that it isn’t the moment to start using it. Then I have adopted the guidelines I have read in several post about preparing for Angular 2, using “as” notation in controller and write directives using “controllerAs”, “bindToController” and isolated scopes.

During these days, learning to implement custom decorators in TypeScript, I came up with a better idea.

Searching differences

Watching how to define the “Angular 2” components and how to define directives in “Angular 1” you can see the equivalences, the logic are on component or controller and the definition are on the decorator or DDO. Then watching this:

var app = angular.module("app", []);
export class DirectiveController {
    static $inject = [];
    texto: string;
    constructor() {
        this.texto = "Hello from the directive controller";
app.directive("myDirective", () => {
    return {
        scope: {},
        template: "<div>{{vm.text}}<div>",
        controllerAs: "vm",
        bindToController: {
            text: "="
        controller: DirectiveController

and watching this:

    selector: "my-directive",
    template: "<div>{{vm.text}}<div>",
    controllerAs: "vm",
    bindToController: {
        text: "="
export class myComponent {
    static $inject = [];
    texto: string;
    constructor() {
        this.texto = "Hello from the directive controller.";

I think the big difference are in the @decorators … how the @decorators works? could I write customs decorators for save metadata about one class and, after, access to this decorators through the class in order to get these metadata?

google(“typescript custom decorators”) =>

Great!! Then I can write some decorators to host the metadata, but … what happen if I use the same decorators name than Angular 2 and I try to use the same style? could I develop for Angular 1 using the same style of Angular 2??

That’s what I’ve done in this project Ng2Emulation

Try to emule the component building style of Angular 2 to use them in Angular 1 and get advantage, thinking in the migration to Angular 2.

Of course the views, the templates, continue working with Angular 1 style, but the components will be similar and the migration effort will be less. With Ng2Emulation you can write your directives, controlers and services using Angular 2 syntax.

Angular 2 emulation

At the moment (December 3, 2015) I have create only @Component and @Inject decorators, the bootstraping and one Angular 1 Wrappper where access to the Angular 1.x module. You can do this:

import {bootstrap, Component} from "Ng2Emulation/Ng2Emulation"
import {DataStore} from "App/Services/DataStore"
import {TodoListComponent} from "App/Components/TodoList"
    template: `
<h1>Ng2 Emulator - Todo list sample</h1>
    selector: "my-app",
    components: [TodoListComponent]
export class AppComponent {
    constructor() {
        // Configuration section.
        DataStore.setInitialValues(["A sopesteque", "Picha liebre", "Zurre mierdas", "Chupa candaos", "Cascoporro"]);

You create a class, that will be the controller, and decorate it with metadata that will be the DDO in order to call “angular.directive”, From “selector” I obtain the directive name (using camelCase function) and the DDO always use “bindToController”, “controllerAs” e isolated scopes. In addition, all properties that you put in the decorator are passed to the DDO, then if you have a directive with code in the “link” or “compile” you can put it in the decorator component.

Of course, If you going out Angular 2 standard you will have to migrate it in the migration moment, if you use Angular 1 things that are not in Angular 2 you will have to rewrite.

Another example here, this time using @Inject:

import {Component, Inject} from "Ng2Emulation/Ng2Emulation"
import {TodoService} from "App/Services/TodoService"
    templateUrl: "TypeScript/App/Components/TodoList.html",
    selector: "todo-list",
    componentAs: "vm"
export class TodoListComponent {
    upper(text) {
        if (text)
            return text.toUpperCase();
        return undefined;
    constructor(@Inject(TodoService) public service: TodoService) {
        this.todoList = service.todoList;
    text: string;
    todoList: string[];
    addTodo() {
        if (!this.text)
        delete this.text;

Now I’m integrating the router, I’m trying ngComponentRouter (before called ngNewRouter) and, of course, add the @RouteConfig decorator.

I would like to have some feedback, comments are welcome!!

One comment

Deja un comentario

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see

Demuestra que no eres un bot *