node-deep-equal VS mocha

This is a pretty hard problem, there are lot's of subtleties even just in defining deep equality. A quick check of a run of the mill implementation will confirm that this is not a problem for a junior: https://github.com/inspect-js/node-deep-equal/blob/master/index.js

So I got a bit curious to look even deeper to this and noticed qs is not the only case where the similar fate has happened. Another package using side-channel is deep-equal and has a similar history. It used to be a very small utility when still in v1.0 series, but starting from v1.1 it had new maintainers and the package size went up while also having performance regressions so people kept using v1.0.

Using something like Vitest, Jest, or Mocha didn't work because:

MochaJS is a feature-rich JavaScript test framework running on Node.js, making it a popular choice for both backend and frontend testing. It's known for its flexibility and straightforward syntax, allowing for asynchronous testing and the use of any assertion library.

We use Jest Framework for testing. Jest is not a dogma, and, of course, in its place can be any other test runner, such as Mocha or Ava. Let's focus on tests. I'll provide a short example because I don’t want to waste your time. You can find the full version here. It's crucial to read the comments in the code below. Let's go!

JavaScript Popular tools for testing: Mocha, Jasmine, Unit JS, Jest

To execute your tests, you can create test scripts using popular testing frameworks like Mocha, Jasmine, or Jest. These frameworks provide a structured way to organize and run your tests, report results, and handle assertions.

⚗️ Mocha and Chai for testing

Testing frameworks like Jest, Mocha, and Jasmine are crucial for software development, ensuring code reliability and correctness. They offer features like test suites, test cases, assertions, and asynchronous testing support.