Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Hidden files (prefixed with a dot) are ignored
See original GitHub issueI noticed this when making changes to my .eslintrc.js file. ESLint errors will not show up in hidden files (files prefixed with a dot).
If I have a file, test.js, with ESLint errors, they are displayed in my editor with a squiggly underline, and in the problems tab. If I re-name the file to .test.js, the VS Code ESLint extension seems to ignore it completely.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Git: how to ignore hidden files / dot files / files with empty file ...
Your answer is very simple: This is the content of your .gitignore file: # ...
Read more >Linux History: How Dot Files Became Hidden Files
The history of hidden files ... Ever wondered why there are files on your Linux system, starting with a dot? The short answer:...
Read more >gitignore Hidden Files with Exceptions - Sal Ferrarello
When setting up my .gitignore file, I like to ignore all these hidden files (with a few exceptions). gitignore All Hidden Files. By...
Read more >How to remove hidden files in Linux - nixCraft
How do I delete hidden files in Linux starting with . (dot) character? Introduction: Linux and Unix like operating system allow users to...
Read more >How to exclude/ignore hidden files and directories in a ...
find . \( ! -regex '.*/\..*' \) -type f -name "whatever" , works. The regex looks for "anything, then a slash, then a...
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
This is standard eslint behavior. If elint is executed in the terminal you get:
I will close the issue since the extension tries to stick with the normal ESLint behaviour.
@leoselig simply configure the
"eslint.workingDirectories"for each workspace package and it should work as expected.