External modules with AMD always requires "exports" even when it is not used

Here's a small external module that explicitly exports a module:

module Foo {
    export var foo = 42;
}
export = Foo;

The code generated for this is:

define(["require", "exports"], function(require, exports) {
    var Foo;
    (function (Foo) {
        Foo.foo = 42;
    })(Foo || (Foo = {}));

    return Foo;
});

This feels like bad AMD since you are requiring the "exports" magic dependency, but then not using it and instead returning Foo directly.

It's annoying for minimal AMD loaders since they can't assume the object return of your module is your "exports" object and have to guess that you really meant to return something that overrode the "exports" object you asked for.

Furthermore, why bother declaring a dependency on 'require' when it's not used?

首先根据 TypeScript 示例复现问题，并比较生成的 AMD 输出。检查 compiler 的 AMD external-module 发射路径及其回归测试（如果存在）。当未使用的 "require" 和 "exports" 依赖不会被发射，同时返回的模块值仍然正确时，即表示完成。