purista
eslint-config-standard
purista | eslint-config-standard | |
---|---|---|
4 | 7 | |
59 | 2,570 | |
- | 0.9% | |
9.5 | 8.6 | |
20 days ago | 6 days ago | |
TypeScript | TypeScript | |
Apache License 2.0 | 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.
purista
-
PURISTA - Thanks to amazing open-source software
GitHub is uses as repository, issue & project tracker, and also for hosting the official website.
-
Do we need a new player in TypeScript event sourcing?
If you like, you can have a look at my stuff at https://purista.dev or ping me. Would be nice to have some conversation about this event sourcing topic.
-
The power of PURISTA TypeScript Framework v1.7
Visit the official PURISTA website purista.dev to learn more about PURISTA v1.7 and embark on a new era of application development. Unleash your creativity, enhance collaboration, and deliver exceptional software solutions with PURISTA TypeScript Framework v1.7.
- Version 1.7 is in progress
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?
megalo - Deno HTTP server framework focused on speed
prettier - Prettier is an opinionated code formatter.
fmodel-ts - Functional Domain Modeling with Typescript
standard - Ruby's bikeshed-proof linter and formatter 🚲
typescript-ddd-example - 🔷🎯 TypeScript DDD Example: Complete project applying Hexagonal Architecture and Domain-Driven Design patterns
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
Visual Studio Code - Visual Studio Code
success-symbol - Cross-platform success symbol.
eslint-plugin-node - Additional ESLint's rules for Node.js
bhai-lang - A toy programming language written in Typescript
infisical - ♾ Infisical is the open-source secret management platform: Sync secrets across your team/infrastructure and prevent secret leaks.
nanocolors - Use picocolors instead. It is 3 times smaller and 50% faster.