Hello,
I published to npm yesterday a new version of my package, but since then SB continues desperately to tell me it does not exist.
I get the following error:
{
"error": "UNSATISFIED_RANGE",
"data": {
"name": "@ng-bootstrap/ng-bootstrap",
"range": "5.1.0"
}
}
I read via this article that Turbo is getting packages via jsDelivr and Unpkg...
So, I double checked everywhere, and my package exists !
npm: https://www.npmjs.com/package/@ng-bootstrap/ng-bootstrap/v/5.1.0
jsdelivr: https://cdn.jsdelivr.net/npm/@ng-bootstrap/ng-bootstrap@5.1.0
unpkg: https://unpkg.com/@ng-bootstrap/ng-bootstrap@5.1.0
It even exists on your side !!
https://t.staticblitz.com/v7/@ng-bootstrap/ng-bootstrap@5.1.0
Is it related to some cache issues? I don't see any other explanation...
On a side note this screen below is not that accurate

Only one of them is faulty (from your point of view, because it exists...) Displaying a proper error message would make it easier for user to investigate what's going on.
Hello,
I published to npm yesterday a new version of my package, but since then SB continues desperately to tell me it does not exist.
I get the following error:
I read via this article that Turbo is getting packages via jsDelivr and Unpkg...
So, I double checked everywhere, and my package exists !
npm: https://www.npmjs.com/package/@ng-bootstrap/ng-bootstrap/v/5.1.0
jsdelivr: https://cdn.jsdelivr.net/npm/@ng-bootstrap/ng-bootstrap@5.1.0
unpkg: https://unpkg.com/@ng-bootstrap/ng-bootstrap@5.1.0
It even exists on your side !!
https://t.staticblitz.com/v7/@ng-bootstrap/ng-bootstrap@5.1.0
Is it related to some cache issues? I don't see any other explanation...
On a side note this screen below is not that accurate
Only one of them is faulty (from your point of view, because it exists...) Displaying a proper error message would make it easier for user to investigate what's going on.