Cannot install latest version of an npm package, possibly caching 4xx from NPM

[cormacrelf]

This is a re-issue of #491, because the problem did not go away by itself.

Basically:

1. Add a package to a blitz
2. I think you need to attempt to install a new version explicitly before publishing or before publish has propagated. I am pretty sure I did that.
3. Publish a new version to NPM
4. StackBlitz cannot find the new version when you try to install it, explicitly or through an update.

Example blitz where this is happening:

• https://stackblitz.com/edit/angular-7fkpzq-y7hb79
• Has version ng2-dragula@2.0.1, we want to upgrade to ng2-dragula@2.0.2
• 2.0.2 was published 5 days ago, and the blitz is still stuck.
• I can install v2.0.2-0 just fine, explicitly or with the @next dist-tag.

Step 4 is impossible to achieve. Here are 3 ways you might try:

• If you refresh, it does not find the new version.
• If you delete and re-add, it does not find the new version.
• If you delete and re-add with an explicit version like ng2-dragula@2.0.2, the UI comes up with an error saying "Failure: unsatisfied version range. Unable to resolve package ng2-dragula@2.0.2".

That Step 2 is necessary leads me to believe that StackBlitz/turbo is caching 4xx/5xx responses from NPM, which is wrong.

[cormacrelf]

Nothing? This is still a problem, 17 days later.

[EricSimons]

@cormacrelf sorry about the delay on this! npm recently started to throttle registry access which sometimes causes our resolver to fall out of sync. I just manually resynced ng-dragula so it should be good to go now, but lmk otherwise 👍

[cormacrelf]

I mean, I’m less concerned about personally not being able to update than the fact that it might happen again to someone else, and that a package stayed in the cache for that long. At least you know. Thanks!

[cmckni3]

I am having issues updating my demo to latest version of ngx-ui-switch. I released 7.0.0 this morning but cannot get stackblitz to update the package.

[EricSimons]

@cmckni3 I was able to install version 7.0.0 - can you try again and lmk? It's possible that the npm registry's response was cached during your initial request

[cmckni3]

Working now. Earlier I kept getting the previous 6.1.1 version. Specifying to install 7.0.0 would result in unsatisfied version range.

I am thinking it was due to the caching.

Thanks!

[bob-lee]

Having the same problem for ng-animate-value@0.0.4. Is there any workaround?

[EricSimons]

@bob-lee I think it should be working now- can you check?

[bob-lee]

@EricSimons thanks it’s working now

[tiliev]

We are experiencing the same issue for igniteui-angular@7.0.2:

But the version is released 4 days ago:

@EricSimons @apai4