import-js/eslint-plugin-import

`no-extraneous-dependencies`: add an option to allow specific package names to be in different categories

Open

#903 opened on Jul 26, 2017

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

Description

It would be great if the import/no-extraneous-dependencies rule could be ignored project wide but only for certain dependencies.

import/no-unresolved already has this functionality with it's ignore regex setting.

This could also be a potential solution for https://github.com/benmosher/eslint-plugin-import/issues/496

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
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.
1-2 days
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.
clear
Prerequisites
ESLint plugin basicsJavaScript regexNode.js environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Study the current implementation of the `no extraneous dependencies` rule in `src/rules/no extraneous dependencies.js`. Look at how `no unresolved` rule implements its `ignore` option (regex pattern) in `src/rules/no unresolved.js`. Propose a similar `ignore` or `allow` option that accepts an array of package names or regex patterns. Reference linked issue #496 and existing comments for additional context. Ensure test coverage for new option.
`no-extraneous-dependencies`: add an option to allow specific package names to be in different categories · import-js/eslint-plugin-import#903 | Good First Issue