import-js/eslint-plugin-import

`import/extensions` flagging when default package export is a json file

Open

#759 opened on Mar 1, 2017

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)JavaScript (1,549 forks)batch import
bughelp wanted

Repository metrics

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

Description

I have a package with a default export of index.json instead of index.js. When I try to import this package:

import foo from 'json-package';

import/extensions complains about the lack of an extensions. This doesn't seem like desired behavior.

fyi: @ljharb

Contributor guide

Research direction
Investigate the `import/extensions` rule handler for package imports; check if it correctly resolves the default export when the package main entry is a JSON file. Look at the rule's implementation to see if it considers `resolve` options like `extensions` and `moduleDirectory`, and whether it handles `package.json` `main` field pointing to a JSON file.
Tech stack
javascript
Domain
developer experiencetooling
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
Node.jsnpmESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75