lodash
jQuery
Our great sponsors
lodash | jQuery | |
---|---|---|
186 | 164 | |
58,716 | 58,812 | |
0.5% | 0.8% | |
5.2 | 8.6 | |
11 days ago | 7 days ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | 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.
lodash
-
Full Stack Web Development Concept map
lodash - utility library enabling things like deep object comparison that aren't easy to do with javascript out of the box. docs
-
JavaScript Libraries That You Should Know
5. Lodash
-
Top 20 Frontend Interview Questions With Answers
It's also important to ensure that you're importing libraries correctly, so webpack can perform tree shaking effectively. For example, let's import lodash, as follows:
-
Coming to grips with JS: a Rubyist's deep dive
lodash and You Might Not Need Lodash
-
Deep Cloning Objects in JavaScript, the Modern Way
A lot of Lodash functions are implemented as combinations of other Lodash functions, so importing a single function actually imports half of Lodash under the hood:
https://github.com/lodash/lodash/blob/main/src/.internal/bas...
-
5 best JavaScript multidimensional array libraries
Lodash is a popular utility library that provides a wide range of methods for dealing with arrays, collections, and objects. Lodash, while not expressly built for multidimensional arrays, may be a useful tool for fundamental array operations.
-
How to secure JavaScript applications right from the CLI
To help you quickly set up a project test with the Snyk CLI, a sample JavaScript project has been made available in this GitHub repository with all the necessary manifest files. The project is a simple quote API that uses Lodash and Express as their dependencies. The quote API has a GET / endpoint that returns a list of quotes and a GET /random endpoint that returns a random quote.
-
Lodash just declared issue bankruptcy and closed every issue and open PR
I don't think isEmpty is O(n) except in the case where the object is a prototype[1] - I assume that's one of those weird JS edge cases - otherwise it does what you expect, which is to iterate with a for-in loop and return on the first iteration, so it is O(1).
[1]: https://github.com/lodash/lodash/blob/4.17.15/lodash.js#L114...
lodash/fp is an optional distribution of lodash that did what the core library did, but did so in a more flexible, powerful, composeable way that makes it easier to construct powerful functions. it was separate from the core, but based heavily on it. https://github.com/lodash/lodash/wiki/FP-Guide
at the time, nothing was settled. we were in a pioneering mode of building; we didn't know what people would find useful or what the future would hold. there were a lot of different ideas floating around, and lodash was trying to stay the same while also offer a port to this barely-subtly-different paradigm, to see what value might be found there. saying that "introduced" it feels like a crude reduction to me; he allowed people the option they asked for.
i personally think fp - in particular - "pointsfree" fp - has huge down sides to being understandable. but it also is a much more succinct and capable way of expressing things, and multiple times a week i run into situations where auto-currying or reverse args would make the code i write much cleaner & not damage code comprehension.
rather than call fp a fad, & insult the author for ever letting it in, i think there's room to say that it's sad that js had to stay on the lowest common denominator. the future was unable to be changed, the old ways stuck. we lost some really good opportunity & capabilities. that said, i still think the pointsfree style is hugely damaging & responsible for greatly reducing the chances we had to improve. instead, we're not "moving on", we're going back to square 1, to the only thing we've ever known or done. that makes me a little sad, to have the pioneering pack up & move back into the city.
The bigger news is that Lodash is migrating from Node.js to Bun: https://github.com/lodash/lodash/commit/97d4a2fe193a66f5f96d...
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
What are some alternatives?
ramda - :ram: Practical functional Javascript
underscore - JavaScript's utility _ belt
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
lazy.js - Like Underscore, but lazier
RxJS
Sugar - A Javascript library for working with native objects.
immutable-js - Immutable persistent data collections for Javascript which increase efficiency and simplicity.
Mout - Modular JavaScript Utilities
cash - An absurdly small jQuery alternative for modern browsers.
Rambda - Faster and smaller alternative to Ramda
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.