is there a way to export more than one module per npm package via typings?

[zpdDG4gta8XKpMCd]

According to typings for npm packages there can be a file specified in the "typings" property or an index.d.ts which implies that there can only be a single typescript module (javascript file + declaration file) per npm package.

Is there a way to export typings for more than one module per npm package?

[falsandtru]

You can export many files in single file:

// a.d.ts
export declare var a1;
export default function a()

// b.d.ts
declare module 'b' {
  export var b1;
  export default function b()
}

// index.d.ts
export * from './a.d';
export {default} from './a.d';
import './b.d';
export * from 'b';
export {default as b} from 'b';

[zpdDG4gta8XKpMCd]

interesting idea

[falsandtru]

And you can define many modules but you should not.

// node_modules/b/types.d.ts
declare module 'a' {
  export var a;
}
declare module 'b' {
  export var b;
}

// node_modules/b/index.d.ts
import './types.d';

// index.ts
import {b} from 'b';
import {a} from 'a';

[zpdDG4gta8XKpMCd]

Mind me asking why shouldn't I?

[falsandtru]

Because you should not override other module typings. It is global namespace pollution.

[blakeembrey]

You can not use ambient modules for the typings field in package.json so those examples would not work. Typings in NPM packages should only ever be external module declarations which limit you to exporting a single module anyway. You should not be exporting more than one module from your NPM package, since the NPM package is itself only one module.

[zpdDG4gta8XKpMCd]

Since when a typescript module is equal to a npm package?
On Nov 26, 2015 8:04 PM, "Blake Embrey" notifications@github.com wrote:

You can not use ambient modules for the typings field in package.json so
those examples would not work. Typings in NPM packages should only ever be
external module declarations which limit you to exporting a single module
anyway. You should not be exporting more than one module from your NPM
package, since the NPM package is itself only one module.

—
Reply to this email directly or view it on GitHub
#5804 (comment)
.

[blakeembrey]

Since when a typescript module is equal to a npm package?

When you publish it on NPM and use their module namespace options, you're publishing your code as a package under a single name that node will use to resolve. You can not have two modules inside the same NPM package, so TypeScript doesn't resolve like that either.

[zpdDG4gta8XKpMCd]

that's not true, you can load separate JavaScript files from under a package:

var sub = require ('npm-module-name/separate-javascript-file');
On Nov 26, 2015 8:17 PM, "Blake Embrey" notifications@github.com wrote:

Since when a typescript module is equal to a npm package?

When you publish it on NPM and use their module namespace options, you're
publishing your code as a package under a single name that node will use to
resolve. You can not have two modules inside the same NPM package, so
TypeScript doesn't resolve like that either.

—
Reply to this email directly or view it on GitHub
#5804 (comment)
.

[blakeembrey]

Perfect, now I understand. I was mixing the terminology of module and package since I'm coming from the NPM ecosystem where they are used interchangeably. Only ambient modules have that ability in the same file. I thought TypeScript resolved the files using that syntax already, but I could be wrong. There's a few more limitations right now that just that in TypeScript, such as not differentiating browser either. I'll leave the TypeScript team to comment more though.

Edit: You can obviously have .d.ts files alongside the .js file and it will work.