Suggestion: multi-file external modules

[RyanCavanaugh]

Support compiling multiple input .ts files into one external module.

Need to determine exactly how the module boundaries are defined when doing this.

[basarat]

👍

[vvakame]

👍

[reverofevil]

I'm highly interested in this issue getting closed. I don't like an idea of concatenating *.ts files in my source directory with a build script.

What do you mean by "module boundaries"?

[basarat]

What do you mean by "module boundaries"?

Given:

a.ts:

export class A{}

b.ts:

export class B{}

---

What will the .d.ts will be?

---

This 1:

declare module 'foo'{
     class A{};
     class B{};
}

or 2

declare module 'foo/a'{
     class A{};
}
declare module 'foo/b'{
     class B{};
}

---

My vote : 1

[reverofevil]

Why should it create a module for each class at all, if we're explicitly making one module file?

My vote goes for the first option.

[basarat]

Support compiling multiple input .ts files into one external module.

@RyanCavanaugh can you append the following as well

Support compiling multiple input .ts files into one external module.
Support generating a definition file .d.ts for such an external module.

If you want I can create a separate issue for that.

[charlessolar]

To add my 2 cents, I agree I would like to see 1, but I know that can be a challenge if for example 2 different files contain the same class or variable name.
I am hoping, that like the CommonJS namespace merging you already do we would simply get a 'multiple declaration' exception.

But either 1 or 2 I would like to see this implemented someway because my application uses requirejs extensively to deliver SPA functionality with durandal.