Found when debugging a different mysterious commonjs bug with @elibarzilay:

1. Install @types/node for this repro. I couldn't get it to repro on a local module, but I think I'm missing something fairly simple.

// @filename: ns.ts
namespace myAssert {
    export type cool = 'cool'
}
var myAssert = require('assert')

// @filename: test.js
exports.equal = myAssert.equal
exports.e

https://github.com/less/less.js/blob/dc3a3105300930e2df14062fcf3de97d43db61b0/packages/less/src/less/tree/ruleset.js#L501
https://github.com/less/less.js/blob/dc3a3105300930e2df14062fcf3de97d43db61b0/packages/less/src/less/tree/debug-info.js#L1

Found this issue when trying to use less from the source. This works in dist because the class is compiled into a function.

### Example
let unreachableProxy = "http://127.0.0.1:8888"
try:
  let client = newHttpClient(proxy=newProxy(unreachableProxy), timeout=1)
  var res = client.getContent("https://github.com")
  echo res
except:
  echo "Timed out"

Current Output

timeout variable is ignored, program stuck until default socket timeout will happen

Expected Output

Timed out a

After ethereum/solidity#10737 we should be able to replace nearly all non-range-based for loops by range-based loops using appropriate ranges.

See scala-js/scala-js#3874 (comment)

Should suppress --strict warnings.