TypeScript/tests/cases/conformance/salsa/assignmentToVoidZero1.ts

// @filename: assignmentToVoidZero1.js
// @declaration: true
// @module: commonjs
// @outdir: auss
// @checkJs: true
// @allowJs: true

// #38552
exports.y = exports.x = void 0;
exports.x = 1;
exports.y = 2;
In JS, assignment to `void 0` isn't a declaration (#39452) Previously, property assignments with `void 0` initialisers were treated like any other values. But this causes us to choke when checking our own commonjs emit. This is something that happens by mistake a fair amount, so this PR goes back to treating these assignments as normal assignments. This should allow us to check our own emit in loose cases without harming other code bases, since `void 0` is rarely written by hand. Note that other errors still happen: noImplicitAny forbids accessing undeclared properties on object literals, and strictNullChecks forbids assigning `undefined` to properties with a different type. However, this change is enough to unblock compilation with `strictNullChecks: false`. 2020-07-06 23:00:12 +02:00			`// @filename: assignmentToVoidZero1.js`
			`// @declaration: true`
			`// @module: commonjs`
			`// @outdir: auss`
			`// @checkJs: true`
			`// @allowJs: true`

			`// #38552`
			`exports.y = exports.x = void 0;`
			`exports.x = 1;`
			`exports.y = 2;`