Guangcong Luo a65faf263f Stop using assert.strict.strictEqual (#7515) ... It turns out that when I switched us from `assert` to `assert.strict`, I didn't actually update any existing tests or tell anyone: 0df0d234f2 So apparently everyone else just kept on using `strictEqual`. This will be a PR and also throw an error if people continue trying to use it, which should make it much clearer what PS policy is on this. A lot of the problem may be that TypeScript marks assert.strict.equal as deprecated when it's not. This was fixed 4 days ago: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/48452 But this probably hasn't made it to a thing yet. Until then, you'll have to deal with TS marking your tests as deprecated, but it shouldn't be too long. Accidentally using `assert` instead of `assert.strict` should now show an error. This protects against the probably much worse mistake of accidentally using `assert.equal` rather than `assert.strict.equal`. `assert.ok` is also deprecated now.		2020-10-14 01:19:03 -07:00
..
chat-commands	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
chat-plugins	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
chat.js	TextFormatter: Support replacing \n without trusted (#7507)	2020-10-11 13:38:34 -07:00
ip-tools.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
ladders.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
modlog.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
room-battle.js	Fix BattleStream test	2020-06-18 22:40:01 -07:00
rooms.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
sockets.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00
users.js	Stop using assert.strict.strictEqual (#7515)	2020-10-14 01:19:03 -07:00