google/closure-compiler

Absolute imports do not auto resolve to index.js files in node resolution mode

Open

#3,698 opened on Sep 29, 2020

View on GitHub
 (3 comments) (1 reaction) (1 assignee)Java (1,197 forks)batch import
help wanted

Repository metrics

Stars
 (7,176 stars)
PR merge metrics
 (Avg merge 3d 4h) (1 merged PR in 30d)

Description

Affects:

Version: v20200927.0.0
Built on: 2020-09-29 11:30

Inputs:

// main.js
import { A } from 'foo';
console.log(A);

// foo/index.js
export const A = 'B';

Command:

java -jar compiler.jar -O ADVANCED --language_out ECMASCRIPT_2017 --module_resolution NODE --js main.js --js foo/index.js

Errors:

main.js:1:0: ERROR - [JSC_JS_MODULE_LOAD_WARNING] Failed to load module "foo"
  1| import { A } from 'foo';
     ^

Expected output: No error

Notes: Relative imports (import { A } from './foo') works as expected, outputs:

'use strict';console.log("B");

Contributor guide

Research direction
Investigate how the compiler resolves absolute module paths and why it does not automatically resolve to index.js files in node resolution mode. Compare with the relative import handling to identify the missing logic.
Tech stack
javajavascript
Domain
tooling
Issue type
Bug
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
JavaClosure Compiler internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40