In JS, module.exports should be aliasable with a var declaration

[sandersn]

Code

// @noEmit: true
// @allowJs: true
// @checkJs: true
// @strict: true
// @Filename: a.js

// from assert
var assert = module.exports = ok;
function fail() {
}
assert.fail = fail;
function ok() {

}
assert.ok = ok;

assert.AssertionError = function (actual, expect) {
    this.name = 'AssertionError';
    this.actual = actual;
    this.expected = expected;
}

Expected behavior:
No errors, and assert results in a module that is callable with exports { ok, fail, AssertionError }.
Actual behavior:
Lots of errors, and no exports, just a callable module.

[sandersn]

This should also be true when the initializer is a call expression, not just an identifier. Here's an example from npm's code:

// @noEmit: true
// @allowJs: true
// @checkJs: true
// @Filename: npm-log.js
// from npm
var EE = require('events').EventEmitter
var log = exports = module.exports = new EE()
log.useColor = function () {
    this.eventNames()
}
log.enableColors = function () {
    this.useColor()
}

// @Filename: npm-cli.js

var log = require('./npm-log')
log.enableColors()
log.useColor()
log.eventNames()

[sandersn]

This is fixed, although it appears to expose a follow-on error with static properties that have this-assignments. I filed #25906 to track it.