[BUG] Circular Dependency between comparator.js and range.js

[silverwind]

There is a circular dependency in semver which rollup will warn about when bundling the module:

classes\comparator.js -> classes\range.js -> classes\comparator.js

Even thought this may work because of Node's resolution mechanism, I'd recommended to refactor.

[isaacs]

We could maybe do this by putting the intersects method in a different file.

[isaacs]

Oh, actually, that's not possible, because anyone doing require('semver/classes/comparator') will get a broken class.

I think this is a legitimate case of two classes that have to reference one another, and the refactor will be rather strained. Is there a way to just tell rollup to be ok with it?

[gp3gp3gp3]

This throws warnings in react native projects with the metro bundler which can't be silenced unless you silence all warnings unfortunately

[maietta]

Yeah, I'm still having this problem in 2023...

[ilbrando]

I'm also having this issue when using rollup to build my package which uses some other packages with a dependency to semver. The semver version used is 7.6.2 (currently the latest). Is there a workaround for this bug?