Typescript, cant load internal module

Question

I m actually learning typescript, and I m facing some problems with internal modules.

In fact, I have three files :

index.ts in which I start my app

///<reference path='RouteManager.ts'/>
import RouteManager = RestifyRouting.RouteManager;

var myManager = new RouteManager();
myManager.init("superpath");

RouteManager.ts that manage my REST routes

///<reference path='RouteParser.ts'/>
module RestifyRouting {

    export class RouteManager {

        routeParser:RouteParser;

        constructor() {

        }

        public init(filePath) {
            this.routeParser = new RouteParser();
            this.routeParser.register("zfaf","callback");
            console.log(filePath);
        }
    }

}

RouteParser which has to parse some string to get some informations

module RestifyRouting {

    export class RouteParser {

        constructor() {

        }


        public register(path, callback) {
            console.log('super register');
        }

    }

}

I have a gulp file that creates my .js and d.ts files and it works great, except for the index.js file. The compiler tells my that RestifyRouting (which is my internal module) is undefined and I dont know why...

Can you help me ?

PS : every files are in the same folder, it's just a learning application.

Thanks for advance

Can you share the tsc command parameters you're using to compile? (i.e. target, module) — Brocco, May 26 '15 at 12:33
Module : commonJS, target : ES3. These are the only parameters I use in my gulp file — mfrachet, May 26 '15 at 12:34

Brocco · Accepted Answer · 2015-05-26T12:51:32.910

As of TypeScript 1.5 the module syntax is aligned with ES6 module syntax and that is what I have been using as well...

You can remove any references to TypeScript modules and just export the classes directly

index.ts

import { RouteManager } from './RouteManager';
var myManager = new RouteManager();
myManager.init("superpath");

RouteManager.ts

import { RouteParser } from './RouteParser';
export class RouteManager {
    routeParser:RouteParser;
    constructor() {}
    public init(filePath) {
        this.routeParser = new RouteParser();
        this.routeParser.register("zfaf","callback");
        console.log(filePath);
    }
}

RouteParser.ts

export class RouteParser {
    constructor() {}
    public register(path, callback) {
        console.log('super register');
    }
}

Keeping modules

If you'd like to keep using internal modules then you have to be sure to export your module as well as the classes inside the module.

// RouteManager.ts
export module RestifyRouting {
  export class RouteManager{}
}

//index.ts
import { RestifyRouting } from './RouteManager';
//usage
var manager = new RestifyRouting.RouteManager();

Something to keep in mind is that you will not be able to import multiple items into the the same name.

// i.e.
import { RestifyRouting } from './RouteManager';
import { RestifyRouting } from './RouteParser';

NOTES the {} syntax in the import statement can allow multiple imports

{ Class1, Class2 }

The {} can be skipped if you exporting a default:

//Source (foo.ts):
export default class Foo{}
//Reference:
import Foo from './foo';
//usage:
class User {
  foo: Foo;
}

There's no way to keep the namespace aspect ? I really like this way of work — mfrachet, May 26 '15 at 12:43
You can, but it is not necessary... I'll add another example — Brocco, May 26 '15 at 12:46
A good explanation of why namespaces in external modules aren't necessary or even recommended: http://stackoverflow.com/questions/30357634/how-do-i-use-namespaces-with-typescript-external-modules — curpa, May 26 '15 at 16:30

Typescript, cant load internal module

1 Answers1