import-js/eslint-plugin-import

import/named for `module.exports`?

Open

#1,145 opened on Jul 30, 2018

View on GitHub
 (10 comments) (6 reactions) (0 assignees)JavaScript (1,540 forks)batch import
help wanted

Repository metrics

Stars
 (4,946 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

Hey, is there any way to enable the import/named rule for module.exports?

Eg:

//lib.js
const toExport = true

module.exports = {
  toExport,
}


//user.js
const {toEpxort} = require('./lib') // here I want it to throw a lint error

console.log(toEpxort)

Contributor guide

Research direction
Investigate how the import/named rule currently checks named exports and extend it to support `module.exports` syntax. Look at the rule's source code, especially the part that resolves imported names. Consider using AST selectors to detect `module.exports` assignments.
Tech stack
javascript
Domain
developer experiencetooling
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.
Half day
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
JavaScriptESLintNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60