Twitter | Chercher | |
ESLint
The fully pluggable JavaScript code quality tool
2 253
Tweets
35
Abonné
12 196
Abonnés
Tweets
ESLint 12 mai
ESLint v5.0.0-alpha.3 has been released:
Reply Retweet Aimer
ESLint a Retweeté
𝙴𝚕𝚒𝚓𝚊𝚑 𝙼𝚊𝚗𝚘𝚛 10 mai
📊 The Front-End Tooling Survey 2018: Results from 5,097 Devs ► Top libs/frameworks jQuery, React, Lodash, Vue, Angular ► npm scripts usage at 47% ► ESLint usage at 61% ► Jest at 22%, then mocha 14%, & jasmine 10% ► 43% don't unit test their code
Reply Retweet Aimer
ESLint a Retweeté
Maarten Van Hoof 8 mai
En réponse à @geteslint
The autofix functionality in , for example, has saved my team and me a TON of time and frustration. Working in modern JavaScript projects hardly ever makes our OCD lash out anymore.
Reply Retweet Aimer
ESLint a Retweeté
Henry Zhu 8 mai
I probably ask about this every few months but always looking for people to help out (triage, PR review, maintenance) with other babel repos (not that we don't need help in Babel itself 😛) (verifying if issues are still in the latest version is helpful)
Reply Retweet Aimer
ESLint a Retweeté
Vikram Kumar 8 mai
“If you are a JavaScript developer and, for some reason, you are forced to pick only one plugin for your code editor, you should pick ESLint.” — 
Reply Retweet Aimer
ESLint a Retweeté
Simon Kollross 4 mai
🔥 Just published "Using ESLint with VueJS and Laravel Mix" 💯
Reply Retweet Aimer
ESLint a Retweeté
Nicky Meuleman 4 mai
Blog post up! Combining ESLint with Prettier to automagically format your JavaScript! Site is still a work in progress with lots of placeholders left.
Reply Retweet Aimer
ESLint a Retweeté
Tim Cheung 🐼 5 mai
I've created an ESLint shareable config to enable Jest globals in Jest test files only, so you don't have to and avoid DRY for new projects. Already saved me a lot of time 💆‍♂️ Also works for linters based on ESLint like XO.
Reply Retweet Aimer
ESLint a Retweeté
Pierre Vanduynslager 4 mai
A new version of XO is out with new rules, better support, and more. Node.js 6 is now required. XO is an ESLint-based linter with lots of goodies and great defaults.
Reply Retweet Aimer
ESLint a Retweeté
Node.js 4 mai
Why and how to use in your project from
Reply Retweet Aimer
ESLint a Retweeté
Yoran Brondsema 2 mai
When you're the sole developer on a project, static analysis tools like ESLint, Rubocop, bullet e.a. are your friend. They take some time up-front to set up but are a huge time-saver long-term. You don't want to spend your time fixing bugs that could have been prevented.
Reply Retweet Aimer
ESLint a Retweeté
Petr Huřťák 30 avr.
Nice plugin to automatically detect backend vulnerabilities like timing attacks, path traversal or regex DoS.
Reply Retweet Aimer
ESLint a Retweeté
Wolf || Jack 1 mai
When you write something silly, but has your back
Reply Retweet Aimer
ESLint a Retweeté
Auth0 1 mai
Tools and processes like 🔧, continuous integration, 🔨, and test coverage, can help you develop better Node.js modules 💎 → 🐻
Reply Retweet Aimer
ESLint 28 avr.
We just released ESLint v5.0.0-alpha.2. Please give it a try!
Reply Retweet Aimer
ESLint a Retweeté
MoOx 25 avr.
-loader probably needs more love (and maintainers). I moved it to -contrib org (because I was asked to) but nobody is contributing… I do the minimum… Even if I I don’t use it anymore! Please help! poke
Reply Retweet Aimer
ESLint a Retweeté
Jacques Favreau 19 avr.
🚨 v1.2.2 of no-dead-code has been published! 🚨 Has a non-breaking change to prefer "removeby" as the annotation, and adds an optional rule config if you want to name it something else.
Reply Retweet Aimer
ESLint a Retweeté
BrendanEich 18 avr.
People should not use raw JS at scale without strict mode and a linter such as , or a full types-checked-at-tooltime compiler such as TypeScript. Raw C before ANSI similar - lint from makefile required for production code
Reply Retweet Aimer
ESLint 17 avr.
En réponse à @frontsideair
We are always looking to improve the experience. If you have ideas, the best way to start is by opening an issue.
Reply Retweet Aimer
ESLint a Retweeté
Shesh 17 avr.
Yep, at we use for all JS/Flow/Typescript projects. We use babel-eslint parser for Flow and typescript-eslint-parser for Typescript. It's helpful to have one config which we can use for the entire org.
Reply Retweet Aimer