Parse error for quoted export/import names

Description

// e.mjs
const a = 'print me';
export { a as "dove" };

// i.mjs
import { "dove" as b } from './e.mjs';
console.log(b);

e.mjs:3:14: ERROR - [JSC_PARSE_ERROR] Parse error. 'identifier' expected
  3| export { a as "dove" };
                   ^

i.mjs:2:9: ERROR - [JSC_PARSE_ERROR] Parse error. '}' expected
  2| import { "dove" as b } from './e.mjs';
              ^

Contributor guide

Tech stack

javascriptjava

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.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

JavaScriptES modules syntaxclosure compiler parser

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

45

Research direction

The issue is a parse error for quoted export/import names (string literals) in ECMAScript modules. The compiler's parser likely needs to accept `StringLiteral` where `ModuleExportName` is expected. Look at the parser source code in the closure compiler repository, specifically around export and import parsing. Check the grammar rules and tokenizer to allow string literals in those positions. The specification references are already provided in the issue.