Unfortunately, this by itself causes a breaking change with how this package is both built and consumed, and I try to adhere to semver as much as possible. I'm working on a v5 that can easily include this change, so I can include it there.

That said, I can piggyback on a simple hack I do for .mjs files that can also be done for cjs. I mention this in the import documentation, but there is a separate micro-memoize/mjs import that is available. I can do the same for CJS, which is not ideal but would likely give you what you need to avoid this error (so long as you use the micro-memoize/cjs) location. If you're willing, I'll spin up a beta of that change that you can test out locally.

I've published 4.2.0-beta.0 with the new micro-memoize/cjs access point, which you should be able to install with just npm install micro-memoize@next. Let me know if this is able to give you what you need for now.