You-Dont-Need-Lodash-Underscore
eslint-config-standard
You-Dont-Need-Lodash-Underscore | eslint-config-standard | |
---|---|---|
25 | 7 | |
18,437 | 2,568 | |
0.4% | 0.8% | |
6.2 | 8.6 | |
21 days ago | 4 days ago | |
JavaScript | TypeScript | |
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.
You-Dont-Need-Lodash-Underscore
- What are some of the best libraries you cannot work without?
-
[AskJS] I love new javascript frameworks and libraries. What are some cool ones?
These are all really outdated tips. Moment is deprecated and it is recommended to use dayJs or date-fns. Lodash is discouraged because it has a huge bundle size and nowadays you will find native functions which do most of the things people have used lodash before. https://github.com/you-dont-need/You-Dont-Need-Lodash-Underscore
-
No Lodash
https://github.com/you-dont-need/You-Dont-Need-Lodash-Unders... seems to be a more readable alternative to this website.
- An NPM package that you love and a package that you hate
-
Migrate jQuery to VanillaJS - UpgradeJS.com
Adjacently useful is https://github.com/you-dont-need/You-Dont-Need-Lodash-Underscore
-
What are your favorite, must-have packages when you're creating a project?
I never used lodash but I found this. Might interest you.
- How to Use Lodash in Svelte?
- Help! I removed unused node modules packages and I optimized the imports but the bundle size does not changed
-
I once tried not to use date-fns
In one of my team's Pull Requests I noticed date-fns being added as dependency for our components library for one usage: transform a timestamp to "MM/yy" string, as it represented a debit card's expiration date. Inspired by You don't (may not) need lodash/underscore, I thought to myself - can't we just implement a 2-digit month and 2-digit year formatting? It looks simple, right?
-
Lodash
Yes and no. We did but are converting to in-house code since most Lodash functions are already available as native JS and/or @babel/preset-env + core-js@latest (see: You don't need Lodash).
eslint-config-standard
-
PURISTA - Thanks to amazing open-source software
eslint-config-standard
-
Setting up ESLINT with TS/JS in your React project in 2023
Based on your requirements and environment, answer the questions accordingly. At least with eslint version 8.0.1, you are only presented with 2 style guides: standard and XO. Personally, I prefer the standard styling guide but at any give time, it is a personal choice and as such feel free to choose any from a bunch of available options. Once all dependencies are installed, ensure that you have the following packages added as devDependencies to your project:
-
[AskJS] favorite JavaScript library
Hmm right, haven't found too many controversial things in https://github.com/standard/eslint-config-standard/blob/master/.eslintrc.json, besides no-semi fixed by semi-standard and comma-dangle "never" (sucks for git history, they should allow it for multiline cases https://eslint.org/docs/rules/comma-dangle#always-multiline)
-
Some tips on tooling for improving our code
ESLint plugin for StandardJS; allows you to format code as StandardJS, but clear more serious errors too.
-
A notable JavaScript developer shamelessly copied one of my most downloaded nod
The JS Open Source Community is filled with people grifting things like this. Quite notably, there's a linter called JS Standard Style, which actually has nothing to do with JS Standards.
It's marketed as if it was a standard, the fact that it isn't is tucked away in the readme, and also -- the entire project is just a wrapper around someones .eslintrc file, yet barely any credit is given to the ESLint devs who do all the work.
Go ahead and read the readme here, https://github.com/standard/standard. Could you genuinely tell this wasn't really a JS Standard at a glance? Could you tell this was just a config file for someone elses work? None of the donations go upstream to eslint by the way.
Hell, the actual config file is hidden inside a sub repo:
https://github.com/standard/eslint-config-standard
which has the audacity to claim
> This module is for advanced users. You probably want to use standard instead :)
It's a config file for someone elses program! Why does this library go through so much effort to hide that it's just someones config file? Why on earth is it called JS Standard Style?
The whole community is filled with slimy nonsense like this.
-
JavaScript Is Weird
Eslint is the default linter. Standard is a curated list of rules with good quality.
https://github.com/standard/eslint-config-standard
I would start with that and tweak what you don't like
-
Getting Started with Next.js - VSCode, ESLint and Prettier
Well done, we managed to set up ESLint using Airbnb’s JavaScript styling guide to our newly created Next.js project. You could have used another popular styling guide like Google, Standard, or even create your own to your liking.
What are some alternatives?
just - A library of dependency-free JavaScript utilities that do just one thing.
prettier - Prettier is an opinionated code formatter.
eslint-plugin-import - ESLint plugin with rules that help validate proper imports. [Moved to: https://github.com/import-js/eslint-plugin-import]
standard - Ruby's bikeshed-proof linter and formatter 🚲
ramda - :ram: Practical functional Javascript
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
eslint-plugin-svelte3 - An ESLint plugin for Svelte v3 components.
success-symbol - Cross-platform success symbol.
babel-plugin-lodash - Modular Lodash builds without the hassle.
bhai-lang - A toy programming language written in Typescript
stdlib - ✨ Standard library for JavaScript and Node.js. ✨
nanocolors - Use picocolors instead. It is 3 times smaller and 50% faster.