jQuery
cash
Our great sponsors
jQuery | cash | |
---|---|---|
164 | 19 | |
58,812 | 6,401 | |
0.8% | - | |
8.6 | 4.5 | |
6 days ago | 26 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jQuery
- Ask HN: Tips to get started on my own server
- jQuery v4.0.0 Beta
-
A step-by-step guide: How to create and publish an NPM package.
NPM packages include a wide range of tools such as frameworks like Express or React, libraries like jQuery, and task runners such as Gulp, and Webpack.
-
TSDocs.dev: type docs for any JavaScript library
Great reference.
To this date, one of the best well-documented code is jQuery: https://github.com/jquery/jquery/blob/main/src/core/init.js
I learned a lot from looking into the code.
-
Top 6 Javascript Libraries You Must Know
jQuery
-
What is jQuery?
Downloading: jQuery is registered as a package on npm. You can install the latest version of jQuery on your terminal with the npm CLI command:
-
Setting JavaScript framework standards ( what’s wrong with the React-set standard and why everyone should be like Svelte)
React is great, yeah, absolutely no lies. Released on May 29 2013 and maintained by Facebook (coughs - “Meta”), it has grown to be the the most used JavaScript framework - or library 🌚, Suppressing Angular and kicking jQuery in the nuts. The standard way of building web apps has so far been defined by this superhuman framework and it’s been the most recommended framework for a long time, but what if it’s about to change?. React, for all its glory sadly is shit ( we all know it, yes. But we won’t admit it), it’s sadly gone down the over complexity road that so many of our beloved frameworks have and has been a messy mud fest. In this article, we will look at some aspects of React’s web standards that are not so brilliant and why Svelte should set the latest standards for JavaScript frameworks and web development. Now you might not agree with me, but hopefully after this is over you’ll take a good look at yourself and say, “maybe this bloke might be right”.
-
Do not drop Sass for CSS
The story of jQuery is analagous to this story with Sass. jQuery helped usher in an era of building reliable websites and web applications. It provided a consistent cross-browser API for working with the DOM. It eventually led to part of the API being adopted by ECMAScript. We can thank jQuery for querySelector().
-
jQuery 3.7.0 is now available - This release has it all: bug fixes, a new method, and a performance improvement. We even dropped our longtime selector engine: Sizzle
TIL jQuery still has nearly 6 million weekly downloads.
-
dd
jQuery - duh
cash
- Stack bun pentru extensie chrome+firefox
-
Migrate jQuery to VanillaJS - UpgradeJS.com
If stock jQuery seems too big and you have a lot of code you'd prefer not to waste time converting, try something like jQuery-slim or cash.
-
jQuery Terminal: JavaScript Web Based Terminal Emulator
It was initially released in 2010. But there is a plan to create version 3.0 that will be rewritten in TypeScript and without dependency on jQuery. The plan is to use a modern Cash library to not modify the code that much.
-
The impact of removing jQuery on our web performance
If you are mainly using jquery for its DOM manipulation¹ rather than for browser compatibility² or things that didn't exist consistently in older browsers³ then there are much smaller libraries that do that job which may be worth looking into. https://github.com/fabiospampinato/cash or https://github.com/franciscop/umbrella to give a couple of examples. Some explicitly support IE11 so you are not dropping as much support for legacy browsers as you might otherwise.
Though if jQuery works for you and isn't a performance issue, then by all means keep with it. It may not be ideal, but good enough and does the job. Let the naysayers spend their time debating whether you should or not, and just get on with making things!
---
[1] selection engine, chained selections, chained modifications, …
[2] not the issue it once was, if you can abandon IE and old Android browsers from your supported UAs or can deal with any issues that crop up individually
[3] again, if you can afford to drop support for legacy UAs
-
Gov.uk drops jQuery from their front end
I think it's a bit of both. jQuery served the purpose of making web development more sane back in the day by handling all browser quirks. Part of that was the nice syntax.
I personally have tried to drop jQuery, but truthfully, its syntax is just much easier to use. Nowadays, I use Cash https://github.com/fabiospampinato/cash to give me the nice syntax without the bloat. It strikes the perfect balance for me.
-
Replacing jQuery (110kb) With UmbrellaJS (8kb)
Cash's maintainer here. I don't think this is true actually.
Zepto supports some methods that Cash doesn't, but you probably shouldn't use them to begin with, like $.ajax, $.isArray, $.fn.animate etc. In 2022 either better built-in solutions exist or better specialized tiny libraries exist.
Everything that is supported by both Zepto and Cash should either work identically or Cash's implementation should be closer to jQuery's. Just to mention one thing in this regard you can run jQuery's test suite with Cash, and Cash's test suite with jQuery, easily [0]. I've done so and looked at every single failed test manually a few times, I doubt nearly the same level of attention went into Zepto. Just to mention one difference: Cash supports jQuery-style event namespacing, Zepto just doesn't support this.
[0]: https://github.com/fabiospampinato/cash/blob/272132a6dc1d885...
-
Show HN: Auto-generate vanilla JavaScript alternatives for jQuery methods
I'm not sure I buy this argument, one can't just say that ~30kb isn't a lot because 30 is a number perceived as low, would 30kb be justified for a library that allows you to toggle a class on a node? Of course it wouldn't, you need to measure what you are getting for 30kb.
I don't buy the second part of the argument either, you can load a 1000kb image on a blog post and that won't have nearly the same effect as loading 1000kb of JS. The JS needs to be parsed and executed and maybe the site doesn't even work without it, the image can probably be rendered progressively, can be decoded in another thread, nothing is really waiting on it to load, and if it doesn't load at all it's not the end of the world anyway.
With ~4kb you can have Preact, is jQuery Slim (~26kb) giving you ~6.5x times as much value as Preact really? Maybe it is, probably not.
For some context I maintain a ~6kb rewrite of a subset of jQuery (https://github.com/fabiospampinato/cash), which IMO is much better value proposition for many use cases.
- It seems to have subtle bugs, like the way the events string is split makes so that double consecutive spaces in it (which can happen as a result of a typo) will result in listening to the empty string event. Basically: 'foo bar'.split ( ' ' ) => ['foo', '', 'bar'].
The `on` method we are using in Cash [1] is a lot more convoluted than that. On one hand it requires more bytes, but on the other the chances of it behaving exactly like jQuery's are much higher. In fact we can also run jQuery's test suite with Cash to spot issues.
Feel free to ping me if you are interested in joining forces.
[0]: https://github.com/fabiospampinato/cash
[1]: https://github.com/sachinchoolur/replace-jquery#on
[2]: https://github.com/fabiospampinato/cash/blob/master/src/even...
jQuery is not tree-shakeable because it uses a chainable API. Like you don't import `toggleClass`, you access the `toggleClass` property of a jQuery instance, so it can't be tree-shaken off automatically.
Even if somebody made a bundler plugin for doing the heavy work jQuery can only be partially compiled with whole modules excluded, you can't exclude individual methods (e.g. you can't just remove `toggleClass`, you have to remove also `addClass`, `removeClass` etc.).
FYI I maintain a jQuery alternative that supports being partially compiled with individual modules turned off, but it requires manually listing them: https://github.com/fabiospampinato/cash
Vanilla JS refers to Javascript that uses native browser methods instead of relying on a library. This is just replacing jQuery with another library constructed on the fly.
I don't see the point and there are already minimal and modern alternatives with the jQuery API like zepto and cash.
1) https://github.com/fabiospampinato/cash 2) https://github.com/madrobby/zepto
What are some alternatives?
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.
Alpine
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
zepto - Zepto.js is a minimalist JavaScript library for modern browsers, with a jQuery-compatible API
umbrella - :umbrella: Lightweight javascript library for DOM manipulation and events
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
anime.js - JavaScript animation engine
three.js - JavaScript 3D Library.
Sass - Sass makes CSS fun!