Closed ghost closed 9 years ago
Thanks for the heads up. I'll try and ping cdnjs early next week and make arrangements. Otherwise, poke me!
I have been taking a look into this... And I can see why they removed the auto update from jPlayer... The skins
not being in the dist
folder would mean they have the /dist/
folder in the url too, after the version.
But... maybe I can jump above the base path and into skins for those. I will have to check with the cdnjs project and see what they recommend.
:+1:
Pull request issued: cdnjs/cdnjs/pull/4103
In case you missed it, I moved the skins to use a SASS build system #260. In the future we can begin adding more variables to enable the changing of colours, widths and other stuff. I expect a new skin will be required to completely enable SASS control of the display.
It looks like the cdn is now up to date with 2.9.2 and I see some other versions being filled in too. I'll review in more detail this afternoon.
I'll also add in cdnjs as our official cdn on the download pages.
If you want to see the HTML for the skins in the CDN, then visit cdnjs/cdnjs/issues/3317 and :+1: it.
It's 2.9.2 here https://cdnjs.com/libraries/jplayer
Closing this thread. The cdn is working fine again for the JS, CSS and images.
We will have to wait till the mustache HTML pages are supported on the CDN, and even then with sensible CORS in order for any HTML hosted there to be of any use.
I think it might be to do with the changearound on your github repo, but https://cdnjs.com/libraries/jplayer is still stuck on jplayer 2.7.1 and I guess quite a few of us rely on that.
Would be great to get it back in sync again - thanks!