mysticatea/eslint-plugin-node

Relative paths to `node_modules` being reported as unpublished

Open

#162 opened on May 6, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)JavaScript (189 forks)github user discovery
acceptedenhancementhelp wanted

Repository metrics

Stars
 (955 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi,

I'm getting no-unpublished-import errors with node_modules-based references:

import Typeson from '../node_modules/typeson-registry/dist/index.js';

This use of paths is convenient in the browser for examples/demos where one doesn't wish to go through a build routine and doesn't need to support older browsers.

Contributor guide

Research direction
Investigate how the no unpublished import rule detects imports and determine why relative paths to node modules are flagged. Look at the rule's source code to see if there is a check for node modules paths and consider adding an exception for such relative imports.
Tech stack
javascript
Domain
backendbuild system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ESLintNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70