Pre-built version of jquery-ui

[MattIPv4]

Hey folks,

We're trying to update jquery-ui on cdnjs, but it looks like this repo as well as the NPM package only distribute jquery-ui in its assorted parts, rather than shipping a pre-built JS bundle like you get if you use the code.jquery.com CDN or the download option on the site.

Is there a distributed version that is pre-built available in an NPM package or tagged git repository anywhere that we can use as the update target for cdnjs? Or, should we just be hosting the content of UI & themes from the NPM package / git repo on the CDN?

Cheers, Matt.

(cc cdnjs/packages#889)

[mgol]

Hey! We distribute the built files to CDNs and share zipped copies of the bundles on the jQuery UI sites. We're not planning any changes here as the project is mostly in maintenance mode.

You can download the full source & theme packages by using the quick download links from the jQuery UI Download Builder page or the 1.13 blog post.

I hope that's enough for you. Thanks!

[MattIPv4]

Unfortunately, downloading from the site won't work for cdnjs -- we either need the files in an NPM package, or in a tagged git repo.

Many users rely on jQuery UI through cdnjs, so it'd be great if y'all could help out here so that we can get the updated version made available to them :)

[mgol]

How do you handle older jQuery UI versions? I think none of them includes built files, don't they?

[MattIPv4]

Looking at our config, we've never updated this library under the new system -- under the old system folks would manually commit files but we no longer permit that for an assortment of reasons (mainly security + infra).

[glensc]

you could perhaps create a branch or tag (jquery-ui-1.13.0.cdn) and put built files there for cdnjs...

[umer936]

Any chance this is going to happen?

[mgol]

Alright, it might be that it's just a question of copying two files from the dist/cdn folder before this line in the release script and then committing them. Since cdnjs is not able to consume what we have right now, let me try this.

If this works (I still need to try it), we could release it as 1.13.2 when it arrives.

(please don't assume it will happen just yet, I am not 100% sure yet if this works)