Regression for eslint output?
See original GitHub issueSetting up new laptop. I’m sure this has worked before, however it is not currently:
> @ lint:src /Users/jblues/mobbiz/LOSMobileApp
> eslint . --ext .ts
/Users/jblues/mobbiz/LOSMobileApp/navigation/AppNavigator.ts
1:8 error 'React' is defined but never used @typescript-eslint/no-unused-vars
✖ 1 problem (1 error, 0 warnings)
Instead of opening editor another app opens.
Latest Webstorm and plugin version.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
Type: Regression [eslint commands] · Issue #47 - GitHub
Running the npm run lint or npm run lint:fix commands, eslint should work properly and/or fix any linting errors if present.
Read more >Command Line Interface - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >node.js - no eslint output - Stack Overflow
Yes, when eslint returns no output, it means there were no issues found. Try running echo $? to see the last commands exit...
Read more >eslint-remote-tester - npm
It's designed to be used when validating regression of new rules. It can be used to spot whether a new rule flags false...
Read more >Streamline JavaScript Development with ESLint - NodeSource
JavaScript is dynamic, and executes behaviors that static languages perform on compile. This is productive, but with a cost. Linting?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It worked after changing file type associations.
@gdelmas I believe if it is found once, OSX will remember, even if the location changes when the next toolbox version comes.
All, please feel free to reopen the issue in collaboration with the project authors. I closed the issue because I was personally satisfied with the workaround, and did not have time to contribute further.