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 GitHub
 (3 comments) (1 reaction) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
bughelp wanted

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

Tech stack
javascript
Domain
developer experience
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.
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.
clear
Prerequisites
basic JavaScriptunderstanding of ESLint rule structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the `import/extensions` rule in the plugin. The issue suggests that when a package's main export is a JSON file (e.g., `index.json`), the rule incorrectly requires an extension in the import. Look at how the rule resolves packages and checks extensions. The fix may involve checking if the resolved module is a JSON file and allowing imports without extension in that case. Consider the configuration options for the rule as well. See the existing tests for the rule and add a test case with a JSON package.