|4 days ago
|6 months ago
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.
🎆 THE BEST AND MOST USEFUL VSCODE EXTENSIONS 🎆
3 projects | dev.to | 22 Feb 2024
In this Thread, I won't show you little extensions that you probably already know, like Live Server or Prettier.
Why is Prettier rock solid?
1.1k isn't bad for a project with ~33 million weekly downloads, imo. Yes, I know that's not necessarily a good metric, but it's ~10 million more than React which also has a similar number of open issues.
Actually that comment derives onto this other issue, where the merits of the decision are discussed:
and to be honest, it didn't look like silly to me :) It was an interesting read for me, who as a maintainer, I tend to give more importance to the official statements such as in this case written recommendations of the source company that defined the new format.
Another example: https://github.com/prettier/prettier/issues/187
That issue has been open for 7 years.
For example, the latest Prettier makes XHTML files invalid by changing DOCTYPE to lowercase:
Prettier moves ts-ignore comments which can cause TypeScript errors:
Interpreting nested CSS functions' "-" as minus and inserting a space:
How can a person that introduces breaking changes in patch release and then just says everyone to piss off when facing critics (just because mister "has needs for this": https://github.com/prettier/prettier/issues/15553#issuecomme...) be a maintainer of such a widespread tool ?
Interestingly, prettier just made a breaking change in a patch release and refused to undo it for a week or so, until a particularly silly pedantic argument won them over.
My only bad experience with prettier, besides the incredible slowness (orders of magnitude slower than ruff)
How to create a good README.md file
5 projects | dev.to | 9 Feb 2024
Command Line Interface Guidelines
8 projects | news.ycombinator.com | 6 Feb 2024
45 NPM Packages to Solve 16 React Problems
22 projects | dev.to | 14 Nov 2023
jshint -> Old library
54 projects | dev.to | 23 Nov 2022
Find ES6 features in any JS code
3 projects | dev.to | 14 Oct 2022
The Why & How To Create A Front-End Website Testing Plan
3 projects | dev.to | 13 Oct 2022
Modern, faster alternatives to ESLint
10 projects | dev.to | 3 May 2022
A Guide to Order: Setting up Prettier and Eslint with Husky, Lint-staged and Commitizen
8 projects | dev.to | 17 Feb 2022
An alternative linter is JShint.
NPM package ‘ua-parser-JS’ with more than 7M weekly download is compromised
13 projects | news.ycombinator.com | 22 Oct 2021
> check out the Web X-Ray repo <https://github.com/mozilla/goggles.mozilla.org/>.
Thanks for example. Peeking a bit under the hood, it appears to be due to transitive dependencies referencing github urls (and transient ones at that) instead of semver, which admittedly is neither standard nor good practice...
FWIW, simply removing `"grunt-contrib-jshint": "~0.4.3",` from package.json and related jshint-related code from Gruntfile was sufficient to get `npm install` to complete successfully. The debugging just took me a few minutes grepping package-lock.json for the 404 URL in question (https://github.com/ariya/esprima/tarball/master) and tracing that back to a top-level dependency via recursively grepping for dependent packages. I imagine that upgrading relevant dependencies might also do the trick, seeing as jshint no longer depends on esprima.
I'm not sure how representative this particular case is to the sort of issues you run into, but I'll tell that reproducibility issues can get a lot worse in ways that committing deps doesn't help (for example, issues like this one are nasty to narrow down).
But assuming that installation in your link just happens to have a simple fix and that others are not as forgiving, how is committing node_modules supposed to help here if you're saying you can't even get it to a working state in the first place? DO you own the repo in order to be able to make the change? Or are you mostly just saying that hindsight is 20-20?
5 projects | dev.to | 29 Sep 2021
Design an Effective Build Stage for Continuous Integration
12 projects | dev.to | 8 Apr 2021
What are some alternatives?
black - The uncompromising Python code formatter
dprint - Pluggable and configurable code formatting platform written in Rust.
prettier-plugin-organize-imports - Make Prettier organize your imports using the TypeScript language service API.
pretty-quick - ⚡ Get Pretty Quick
markdownlint-cli - MarkdownLint Command Line Interface
intellij-rainbow-brackets - 🌈Rainbow Brackets for IntelliJ based IDEs/Android Studio/HUAWEI DevEco Studio/Fleet
spotless - Keep your code spotless
husky - Git hooks made easy 🐶 woof!