[Bug] Changes between 8.5.1 & 9.0.0 introduce a circular dependency

[o-alexandrov]

Description

Changes between 8.5.1 & 9.0.0 introduce a circular dependency

Reproduction

Bundle w/ rollup 8.5.1 (previous version) & then 9.0.0.
You'd see no issues w/ 8.5.1.
And w/ 9.0.0 you'd see the following in your console:

Circular dependency:
../../node_modules/jsonwebtoken/node_modules/semver/classes/comparator.js ->
../../node_modules/jsonwebtoken/node_modules/semver/classes/range.js ->
../../node_modules/jsonwebtoken/node_modules/semver/classes/comparator.js

[rxuxr]

Hi,
I believe I am looking at a similar issue.
After I bumped from 8.5.1 to 9.0.0 in one of our packages bundled by Rollup, there was no error at the build/bundling stage.
However, when importing from this package in our react app, I am seeing the following errors:
TypeError: Cannot destructure property 'ANY' of 'Comparator$1' as it is undefined.

[ricardasjak]

Same issue using Vite (Rollup under the hood), only with prod build.

[david-renaud-okta]

This is a bug in rollup and/or semver See - npm/node-semver#381

[kristoffer-hiddengem]

Taking a (non-dev-)dependency on a buggy package could be considered a bug 😅 Maybe we can check Node support in another way? I'm not entirely sure I understand the 9.0.0 PR, but it seems that on older versions of Node, the checks based on asymmetricKeyDetails is simply skipped, if the semver of process version matches something. How about just skipping the checks if asymmetricKeyDetails is not present?