My 2 cts here: I had similar issues where a package was not found that was definitely in the repository, and clearing the cache fixed it. Does yarn cache clean fix the issue?
So I just tried installing glob10.3.10 using npm by myself (in isolation), and it also failed.
It appears that there is an issue with the npm repository caching.
After using npm cache clean --force the issue went away.
Installing glob10.3.10 using yarn worked out of the box (yarn version 1.22.19).
OK so thanks to your help, I believe the issue was the version of Yarn I am using, which was set to yarn@4.0.1. when downgrading this to yarn@1.22.19 the error clears
Is there a version file for the yarn version in radicle? If so, you may want to consider adding a new issue / PR in the radicle repository about this. A yarn version should be locked in that does not have this issue.
I don’t see a locked yarn version anywhere, but others will know more about this than me. i’ll wait to see if anyone responds here, if not will open a PR.