How to specify eslint config
See original GitHub issueI’m getting a lot of lint errors in the report, and it’s because plato is not picking up my .eslintrc any thoughts?
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Configuration Files - ESLint - Pluggable JavaScript Linter
ESLint supports adding shared settings into configuration files. Plugins use settings to specify the information that should be shared across all of its...
Read more >Eslint Basic Configuration - Medium
How to configure ESLint for Javascript Development and setup in Visual Studio Code, WebStorm, Atom and Sublime. If you don't use it already, ......
Read more >How to Setup ESLint .eslintrc Config - Duncan Leung
The env property in .eslintrc declares which environments your code is expected to run in. Each environment brings with it a certain set...
Read more >How to Create Your Own ESLint Config Package
First you'll need to create a new folder and npm project. By convention, the module name begins with eslint-config- , such as eslint-config-test ......
Read more >eslint-define-config - npm
Provide a defineConfig function for .eslintrc.js files. Latest version: 1.12.0, last published: 2 months ago.
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 Free
Top 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

@keenahn , @gknapp , @pats , @texels I have a released a new version, I added the offending plugin as a dependency directly. (it had better find it now, right?) I tested installing and it worked for me with both yarn and also standard npm.
I want you to try this version and see how it goes.
I’m closing the issue, but if the problem is still there, just post the stack trace like @gknapp did and I’ll dig deeper.
Thank you all for reporting the issue ❤️
hey @gknapp thanks for the feedback (and the stack trace!!) , I think that permissions could be related, but its good to see the ‘problem module’ is ‘eslint-plugin-react’