For reference, the correct ordering is: NEGATIVE_INFINITY < MIN_SAFE_INTEGER < 0 < MIN_VALUE < EPSILON < MAX_SAFE_INTEGER < MAX_VALUE < POSITIVE_INFINITY

All four Number constants emit wrong Lua — they all end up as inf or -inf:

Also MIN_SAFE_INTEGER and MIN_VALUE were emitting identical code, same for MAX_SAFE_INTEGER and MAX_VALUE.

You can verify with:

console.log("MAX_SAFE_INTEGER:", Number.MAX_SAFE_INTEGER);  // 9007199254740991
console.log("MIN_SAFE_INTEGER:", Number.MIN_SAFE_INTEGER);  // -9007199254740991
console.log("MIN_VALUE:", Number.MIN_VALUE);                // 5e-324
console.log("MAX_VALUE:", Number.MAX_VALUE);                // 1.7976931348623157e+308

See Number on MDN for the correct values.

Repro in the TSTL playground: https://typescripttolua.github.io/play/#code/5.4/MYewdgziA2CmB00QHMAUAiAsgQQBoH0BlbAMQFF8BJAOQBUyBxMgJQC50AaAAmoFcBbAEawATvBwFi5KnUYsAlAG4uXAPSquATgAM2gOwBGTZoBMAVgAsei9uMGAUKEgwESNFhpFSFGvSZtOHgFhMUxPKR9ZfyUVdS4AWh19I1NLa1tNBycoOEQUDDDqfAA1bAAZAFUydm4+IVFxT1LKshiVdo7OtQ0zWHiAZhMLR3Ac13ysPBLyqpqg+tCp5qq2rrXurgN4PU09ADZNfoN+iwAOPZMjsz1YAGp+7VOgA

The existing test didn't catch this because it used expectToEqual(true) with comparisons that the wrong values accidentally satisfied (e.g. -inf <= -inf is true). Switched to expectToMatchJsResult with stricter comparisons that actually verify the ordering and specific values.