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 (7,176 stars) (1,197 forks)batch import
help wanted

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

Tech stack
javajavascriptnodejs
Domain
toolingcli
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java programmingJavaScript module resolutionClosure Compiler internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the Node module resolution implementation in the Closure Compiler. Check the code that handles the ' module resolution NODE' flag and how it resolves bare specifiers to index.js files. Look for any known differences between relative and absolute imports in the resolution logic. The issue is reproducible with the provided files and command.