Cdnjs: twitter-bootstrap version not found!

[wangkanai]

https://cdnjs.com/libraries/twitter-bootstrap

Is the something wrong with twitter-bootstrap?

But i still see it in the search

So this issue is causing my build to fail this morning.

[stepkillah]

Same issue for few more packages:
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider

[echolet]

Same issue with Foundation related packages:

https://cdnjs.com/libraries/foundation
404 Not Found

[Dennis-Petrov]

The same is for https://cdnjs.com/libraries/bootswatch

[MattIPv4]

@xtuc looks like the new package generation script has further issues?

Looking at the API response, it seems the library is capped to only 10 versions. It also looks like these are the oldest 10 versions available. https://api.cdnjs.com/libraries/twitter-bootstrap

[wangkanai]

I just did i check and find see that the issue is more wider spread.

Well, i'm not familiar with your code base, So I don't know how to help out. Is there a PR or branch working on this issue?

[MattIPv4]

My guess is that this would be affecting any library with more than 10 versions available on cdnjs. We're actively working to get this fixed :)

[xtuc]

This issue is now resolved. Sorry for the inconvenience

[maxd]

@xtuc The libman (Library Manager, .NET Core JS package manager) is still return errors:

libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider 
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider 
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider

[MattIPv4]

I think the API cache will need clearing - @xtuc do you have the correct access on the cdnjs.com Cf dash to perform a purge?

[wangkanai]

This look like a good results

and build is now passing also

Thank you very much for such a quick fixed on the last work day of the year there mate.

[MattIPv4]

Sweet, glad to hear it's now working for you :)

[jtriance]

Looks like jquery.tablesorter is also not working

[MattIPv4]

Working for me. Try force refreshing the page @jtriance?

[jtriance]

OK, that worked now I just need to figure out how to fix my build. Thanks

[echolet]

Although https://cdnjs.com/libraries/foundation is no longer a 404, the package files have a reduced menu, e.g. no "copy SRI".

[MattIPv4]

I believe SRI calculations aren't running for new library versions. cc @xtuc

[xtuc]

I confirm, we are currently refactoring a lots of things and I had to disable SRI calculations in the meantime.

[justintoth]

I'm still having this issue when downloading packages within Visual Studio, using libman.json.

Restore operation started...
Restoring libraries for project Web
The "[email protected]" library could not be resolved by the "cdnjs" provider
The "[email protected]" library could not be resolved by the "cdnjs" provider
The "[email protected]" library could not be resolved by the "cdnjs" provider
The "[email protected]" library could not be resolved by the "cdnjs" provider
The "[email protected]" library could not be resolved by the "cdnjs" provider
Restore operation completed with errors
Time Elapsed: 00:00:00.2478784
========== Finished ==========

[justintoth]

For others using Visual Studio and libman.json, I resolved the issue by running the "libman cache clean" command.

[Dennis-Petrov]

@justintoth , thank you. But where libman should be located? Especially in case of build server (only build tools are installed)?

[maxd]

@Dennis-Petrov dotnet tool install -g <tool> install tool to $HOME/.dotnet/tools. This directory is not included to $PATH usually. So, you can include it to $PATH env. variable to execute in from any directory or execute libman directly from this directory:

cd $HOME/.dotnet/tools
./libman cache clean

[Dennis-Petrov]

@maxd This looks like linux-specific solution. Anyway, manually deleted folder .librarymanager\cache from user profile. The error has gone.