ImportSpecifier.propertyName should allow string literals

[Josh-Cena]

Bug Report

🔎 Search Terms

import specifier, property name, ModuleExportName, named import

🕗 Version & Regression Information

• This is the behavior in every version I tried

⏯ Playground Link

Playground link with relevant code

💻 Code

import { "useState" as useEffect } from "react";

🙁 Actual behavior

Parser error

🙂 Expected behavior

This should be parsed as valid code and properly type-checked. According to ES spec, ImportSpecifier can be ModuleExportName as ImportedBinding, where ModuleExportName includes StringLiteral.

Babel parses this correctly.

Accordingly, this should be also allowed:

const a = 1;
export { a as "a-b" };

[Josh-Cena]

I'm self-claiming this because no-one seems to be working on it at the moment. It's much more non-trivial than I thought, so if I failed to prepare a PR by this weekend I can be seen as automatically stepping out.

[Josh-Cena]

Duplicate of #40594 it seems 🤔