Accessing the latest version x.y.z releases by x.y or x about cdnjs HOT 19 CLOSED

I'd really like for latest or last to work. Useful also in examples of how to use libraries.

from cdnjs.

This is most likely out of our scope for now, we are trying to keep management overheads down.

Though will keep the ticket alive if anyone has any good ideas. Symlinks sounds like the way to go but I'm not sure I want to be managing hundreds of symlinks etc

from cdnjs.

So there's a few issues with implementing this:

• It assumes everyone follows semantic versioning in the same manner
• Depending on the Cache-Control max-age you might not actually get bug fixes for a long time (e.g. 1 year)
• I'm not sure how we would implement this from a technical sense
  • Right now everything is just static file serving. Introducing somewhat dynamic script serving will complicate things

In regards to including the version number in the file name, my policy is to include the file exactly as it is provided by the library maintainer, filename and all, e.g. http://code.jquery.com/jquery-1.8.0.min.js

from cdnjs.

• Well, one should of course know the library one uses. It's also not like one would have to include such a version. (and a lot of different libraries for sanity reasons follow this or similar semantics)
• Isn't that what ETags are for?
• Would symlinks be an option? That way they'd implemented just like most libraries in Unix systems, which do exactly what I propose here. But I don't know if and how git supports links.

from cdnjs.

I’d also appreciate this, in my case for jQuery as well. It would be great to automatically benefit from bug fix releases (third digit) without having to monitor bug fix releases and updating paths every time.

I understand this may be complicated because it needs adjustments to the existing architecture, but I think it would make a great additional to the service.

from cdnjs.

Thanks @hpatoio

from cdnjs.

#612

from cdnjs.

In #1495 I offered to make a shell script that would manage the multitude of shell scripts and it could be added as part of your build process. @ryankirkman had a concern that any sort of complexity might not work. Have symlinks even been tried? If not, I'd be happy to give a pull request that would add symlinks for a single project to save on clutter. It appears that the CDN might just proxy the first request through to another host, so I suppose it's more important to see if the original host supports symlinks.

from cdnjs.

👍 It will be a cool and needed feature.

from cdnjs.

Tagging in #987

from cdnjs.

👍 nice idea ;)
whats your schedule for do it ?

from cdnjs.

If not wild card support, how about using "latest", especially for libs that use the npm hook - in npm there always is a latest tag. That could even promote moving to verified sources (npm) for the libs, and reduce manual submissions.

from cdnjs.

Completely agree with that, i guess having a /latest/.js and /latest/.min.js would be easier to maintain rather than using wildcards

from cdnjs.

Do you forgot this feature/issue ?!

from cdnjs.

👍

from cdnjs.

+1

from cdnjs.

+1

from cdnjs.

+1

from cdnjs.

Closing, there is no feasible way to implement this whilst we have a focus on asset integrity with SRI.

from cdnjs.