jQuery 3.1.1 Released!
jQuery 3.1.1 is now available!
This release includes some bug fixes and improvements. As with all patch version releases, there are no new features or intended compatibility issues (if upgrading from jQuery 3.0+) in this release.
We fixed a selector issue with disabled options, exposed
jQuery.noConflict even when jQuery is loaded with AMD, and fixed some issues concerning whitespace. We also fixed an issue with the map file that will help when using CDN copies during debugging.
If you haven’t yet upgraded to jQuery 3+, please have a look at the 3.0 Upgrade Guide. The jQuery Migrate 3.0 plugin will help you to identify compatibility issues in your code.
Please try out this new release and let us know about any issues you experienced.
GitHub changelog: Issues fixed in 3.1.1 | All changes
You can get the files from the jQuery CDN, or link to them directly:
You can also get this release from npm:
npm install email@example.com
Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for all your web animations. Along with the regular version of jQuery that includes the ajax and effects modules, we’ve released a “slim” version that excludes these modules. All in all, it excludes ajax, effects, and currently deprecated code. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 6k gzipped bytes smaller than the regular version – 23.6k vs 30k. These files are also available in the npm package and on the CDN:
These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.
Many thanks to all of you who participated in this release by testing, reporting bugs, or submitting patches, including Oleg Gaidarenko, Michał Gołębiowski, Richard Gibson, Alexander Lisianoi, Steve Mao, Dave Methvin, and the whole jQuery team.
What happened to writing a real changelog?
@Dobie We still do manually constructed change logs when there are more commits to talk about. In a patch version like this, there aren’t really enough changes to warrant it. That said, we’ve never had a change log in the format you’ve linked (i.e. a separate file that maintains the full history of changes). While that might be useful in certain cases (and it’s being considered), the blog post can fulfill some of the same purposes in a more conversational style. If you need any help upgrading, we do maintain the upgrade guide and jQuery migrate plugin.
I’ve tried Angular, Iconic etc for building web apps… however I keep coming back to JQuery because its just so easy. All these frameworks complicate JS while JQ just makes it easier…. no wonder jQuery has become such a defacto within web design. Keep up the great work guys
i am starting to learn jq now,thnaks for your help
thank you very much
it can help me
this post is very nice! thanks
Thank you very much!
Downloaded …. thanks!
While that might be useful in certain cases (and it’s being considered), the blog post can fulfill some of the same purposes in a more conversational style.
It is time to update my jquery files. Nice!!!