import-js/eslint-plugin-import

How to include hidden files in settings

Open

#930 opened on Sep 18, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
bughelp wanted

Description

I use neomake (vim plugin) which creates temporary files for "on the fly linking", for a normal file src/foo/Bar.test.js you get src/foo/.Bar.test.js@neomake_123_2.js

I have "no-extraneous-dependencies" rule enabled like in your example (just with more paths):

"import/no-extraneous-dependencies": ["error", {"devDependencies": ["**/*.test.js", "**/*.spec.js"]}]

from https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md

How do you specify that files like "**/.*.test.js" are also ok to use dev dependencies?

I tried:

  • **/.*.test.js doesn't exclude the files
  • **/\.*.test.js triggers an error in eslint config parser
  • **/\\.*.test.js doesn't exclude the files

Contributor guide

Tech stack
javascript
Domain
tooling
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue asks how to include hidden files in the config pattern for the no extraneous dependencies rule. Review the rule's documentation at docs/rules/no extraneous dependencies.md and the underlying glob matching implementation, likely in the rule source or utils. Check if the glob pattern supports files starting with a dot (hidden files). If not, a solution might involve escaping the dot or modifying the glob matching logic. Consider whether the user's neomake temporary files are a common case worth documenting.