eslint-config-canonical
roarr
Our great sponsors
eslint-config-canonical | roarr | |
---|---|---|
7 | 5 | |
570 | 1,026 | |
- | - | |
8.2 | 7.7 | |
3 months ago | 16 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
eslint-config-canonical
-
ESLint-config-canonical: 1k rules ESLint rules
https://github.com/gajus/eslint-config-canonical
I will repost this every couple of years, as it now has been 8 years since I regularly update this config. For most projects, adopting this is going to be as simple as:
{
- Show HN: Canonical – 1k ESLint rules to automate code conventions
-
semver: v1 vs v1000
It's something that keeps coming up in GitHub issues on my various projects... they point at my project version, which could be v7, v28, v33, and then say "This project versioning is bad." or "This project API is unstable.", etc. and then compare them to projects that are v1, as if that somehow proves their point.
-
Why is is prettier used if eslint can format?
For anyone would would like to migrate from Prettier to ESLint, https://github.com/gajus/eslint-config-canonical covers everything that Prettier does and a lot (a lot) more.
-
ESLint plugin for Storybook
Should we add it to https://github.com/gajus/eslint-config-canonical ?
- eslint-config-canonical: 1,000+ rules ESLint rules
roarr
-
semver: v1 vs v1000
It's something that keeps coming up in GitHub issues on my various projects... they point at my project version, which could be v7, v28, v33, and then say "This project versioning is bad." or "This project API is unstable.", etc. and then compare them to projects that are v1, as if that somehow proves their point.
-
Should you have a console.log() in your catch block?
Before you go Winston / Bunyan, give Roarr a shot.
- Real-time log monitoring in the browser using Node.js
- Node.js logging best practices
-
Best practices for logging?
For JSON logging in Node.js, check out https://github.com/gajus/roarr
What are some alternatives?
eslint-plugin-unicorn - More than 100 powerful ESLint rules
angular-logger - Application example built with Angular 15 and adding the log component using the ngx-logger library.
quick-lint-js - quick-lint-js finds bugs in JavaScript programs
apollo-log - A logging extension for the Apollo GraphQL Server
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
tamperchrome - Tamper Dev is an extension that allows you to intercept and edit HTTP/HTTPS requests and responses as they happen without the need of a proxy. Works across all operating systems (including Chrome OS).
eslint-plugin-canonical - ESLint rules for Canonical ruleset.
roarr-cli - A CLI program for processing Roarr logs.
eslint-plugin-storybook - 🎗Official ESLint plugin for Storybook
semantic-release - :package::rocket: Fully automated version management and package publishing
eslint-config-prettier - Turns off all rules that are unnecessary or might conflict with Prettier.
typescript-express-starter - 📘 Quick and Easy TypeScript Express Starter