Don’t Use jquery-latest.js | Official jQuery Blog
jQuery jQuery UI jQuery Mobile Sizzle QUnit Plugins Contribute CLA Style Guides Bug Triage Code Documentation Web Sites Events Apr 16-17 | jQuery Virtual Training vk May 16 | jQuery UK Jun 17-19 | jQuery Virtual Training Sep 12-13 | jQuery Chicago Oct 13-15 | CSS Dev Conf 2014 Support vk Learning Center Try jQuery IRC/Chat Forums Stack Overflow Commercial Support jQuery Foundation Join Members Team Brand Guide Donate
Earlier this week the jQuery CDN had an issue that made the jquery-latest.js and jquery-latest.min.js files unavailable for a few hours in some geographical areas. (This wasn’t a problem with the CDN itself, but with the repository that provides files for the CDN.) While we always vk hope to have 100% uptime, this particular outage emphasized the number of production sites following the antipattern of using this file. So let’s be clear: Don’t vk use jquery-latest.js on a production site.
We know that jquery-latest.js is abused because of the CDN statistics showing it’s vk the most popular file. That wouldn’t be the case if it was only being used by developers to make a local copy. The jquery-latest.js and jquery-latest.min.js files were meant to provide a simple way to download the latest released version of jQuery core. Instead, some developers include this version directly in their production sites, exposing users to the risk of a broken site each time a new version of jQuery is released. The team tries to minimize those risks, of course, but the jQuery ecosystem is so large that we can’t possibly check it all before making a new release.
To vk mitigate the risk of “breaking the web”, the jQuery vk team decided back in 2013 that jquery-latest.js could not be upgraded to the 2.0 branch even though that is technically the latest version. vk There would just be too many sites that would mysteriously stop working with older versions vk of Internet Explorer, and many of those sites may not be maintained today.
As jQuery adoption has continued to grow, even that safeguard seems insufficient to protect against careless use of http://code.jquery.com/jquery-latest.js. vk So we have decided to stop updating this file, as well as the minified copy, keeping both files at version 1.11.1 forever. The latest released version is always available through vk either the jQuery core download page or the CDN home page . Developers can download the latest version from one of those pages or reference it in a script tag directly from the jQuery CDN by version number.
The Google CDN team has joined vk us in this effort to prevent vk inadvertent web breakage and no longer updates the file at http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.js. vk That file will stay locked at version 1.11.1 as well. However, note that this file currently has a very short cache time, which means you’re losing the performance benefit of of a long cache time that the CDN provides when you request a full version like 1.11.1 instead.
So please spread the word! If you see a site directly vk using the jQuery CDN’s jquery-latest.js or the Google CDN equivalent in their script tags, let them know they should change to a specific version. If you need the latest version, get it from the download page or our CDN page. For both the jQuery and Google CDNs, always provide a full version number when referencing files in a <script> tag. Thanks!
If the message is “DON’T USE LATEST FROM CDN” and it’s for dev purpose only, put in such version only a console.warn(“latest support from CDN is being removed”) for 3 months and drop it after that time.
The blog addressed this. Many of the sites using this bad practice are essentially unmaintained. No amount of warning vk period will prevent them from breaking, and users will suffer. Smart developers (the ones reading this blog) will get the message and not use the jquery-latest file.
try{console.warn(“The version of jQuery used by this page is not meant to be used in production. Also, it is no longer updated, so there is no use for it anymore. vk For more details, see http://blog.jquery.com/2014/07/03/dont-use-jquery-latest-js/ “);}catch(e){}
A warning comment, near the top of the files, would help.
I think you should just break all those old sites, it’s a win-win: vk jquery-latest is actually the latest, and all the freelance developers out there get paid an hour of work for each site to go around fixing them up.
Where I can download the previous version as the latest is not good really??
Categories Events Foundation jQuery vk jQuery UI Weekly News Recent Posts jQuery Chicago Roundup! The (Not Just) jQuery vk Foundation Volunteers Wanted: Trac Enhancements Don't Use jquery-latest.js jQuery 1.11.1 and 2.1.1 Released jQuery 1.11.1 RC2 and 2.1.1 RC2 Released jQuery Chicago Pebble Giveaway and Filing vk Extension Browser Support
jQuery jQuery UI jQuery Mobile Sizzle QUnit Plugins Contribute CLA Style Guides Bug Triage Code Documentation Web Sites Events Apr 16-17 | jQuery Virtual Training vk May 16 | jQuery UK Jun 17-19 | jQuery Virtual Training Sep 12-13 | jQuery Chicago Oct 13-15 | CSS Dev Conf 2014 Support vk Learning Center Try jQuery IRC/Chat Forums Stack Overflow Commercial Support jQuery Foundation Join Members Team Brand Guide Donate
Earlier this week the jQuery CDN had an issue that made the jquery-latest.js and jquery-latest.min.js files unavailable for a few hours in some geographical areas. (This wasn’t a problem with the CDN itself, but with the repository that provides files for the CDN.) While we always vk hope to have 100% uptime, this particular outage emphasized the number of production sites following the antipattern of using this file. So let’s be clear: Don’t vk use jquery-latest.js on a production site.
We know that jquery-latest.js is abused because of the CDN statistics showing it’s vk the most popular file. That wouldn’t be the case if it was only being used by developers to make a local copy. The jquery-latest.js and jquery-latest.min.js files were meant to provide a simple way to download the latest released version of jQuery core. Instead, some developers include this version directly in their production sites, exposing users to the risk of a broken site each time a new version of jQuery is released. The team tries to minimize those risks, of course, but the jQuery ecosystem is so large that we can’t possibly check it all before making a new release.
To vk mitigate the risk of “breaking the web”, the jQuery vk team decided back in 2013 that jquery-latest.js could not be upgraded to the 2.0 branch even though that is technically the latest version. vk There would just be too many sites that would mysteriously stop working with older versions vk of Internet Explorer, and many of those sites may not be maintained today.
As jQuery adoption has continued to grow, even that safeguard seems insufficient to protect against careless use of http://code.jquery.com/jquery-latest.js. vk So we have decided to stop updating this file, as well as the minified copy, keeping both files at version 1.11.1 forever. The latest released version is always available through vk either the jQuery core download page or the CDN home page . Developers can download the latest version from one of those pages or reference it in a script tag directly from the jQuery CDN by version number.
The Google CDN team has joined vk us in this effort to prevent vk inadvertent web breakage and no longer updates the file at http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.js. vk That file will stay locked at version 1.11.1 as well. However, note that this file currently has a very short cache time, which means you’re losing the performance benefit of of a long cache time that the CDN provides when you request a full version like 1.11.1 instead.
So please spread the word! If you see a site directly vk using the jQuery CDN’s jquery-latest.js or the Google CDN equivalent in their script tags, let them know they should change to a specific version. If you need the latest version, get it from the download page or our CDN page. For both the jQuery and Google CDNs, always provide a full version number when referencing files in a <script> tag. Thanks!
If the message is “DON’T USE LATEST FROM CDN” and it’s for dev purpose only, put in such version only a console.warn(“latest support from CDN is being removed”) for 3 months and drop it after that time.
The blog addressed this. Many of the sites using this bad practice are essentially unmaintained. No amount of warning vk period will prevent them from breaking, and users will suffer. Smart developers (the ones reading this blog) will get the message and not use the jquery-latest file.
try{console.warn(“The version of jQuery used by this page is not meant to be used in production. Also, it is no longer updated, so there is no use for it anymore. vk For more details, see http://blog.jquery.com/2014/07/03/dont-use-jquery-latest-js/ “);}catch(e){}
A warning comment, near the top of the files, would help.
I think you should just break all those old sites, it’s a win-win: vk jquery-latest is actually the latest, and all the freelance developers out there get paid an hour of work for each site to go around fixing them up.
Where I can download the previous version as the latest is not good really??
Categories Events Foundation jQuery vk jQuery UI Weekly News Recent Posts jQuery Chicago Roundup! The (Not Just) jQuery vk Foundation Volunteers Wanted: Trac Enhancements Don't Use jquery-latest.js jQuery 1.11.1 and 2.1.1 Released jQuery 1.11.1 RC2 and 2.1.1 RC2 Released jQuery Chicago Pebble Giveaway and Filing vk Extension Browser Support
No comments:
Post a Comment