Tomasz Pluskiewicz

I think that @andrewbranch's suggestion was the necessary detail needed to ensure backwards compatibility. And many popular packages have already become ESM-only so I think chai is already in the...

@jakebailey I created a test project using some the WIP v5 types: https://github.com/tminuscode/chai-5-types I found a small mistake in the `use` function and fixed it, so that's good. More interestingly,...

There is, however, one small detail, again relating to `chai-spies` and `chai-json-schema`. Their (recommended?) usage in v4 is like ```ts import chai from 'chai' import chaiSpies from 'chai-spies' chai.use(chaiSpies) //...

> People currently have to change from a default import to upgrade to v5 right? So that is already a known upgrade cost Fair enough. Than we should be good,...

Ready to merge

That's kinda the thing, I don't. There are only 2 mentions of `lazy_transform` in my entire working directory ```shell > find . -type f | xargs egrep -i lazy_transform node_modules/watchpack-chokidar2/node_modules/fsevents/build/config.gypi:...

Any ideas? For now I patched this locally but again, why is that module trying to import `../crypto/util.js` which does not exist?