Import assignment should work with esnext targets

Search Terms

import assignment

Suggestion

#22321 was closed by a bot that thought the issue was addressed, but it wasn't.

Import assignment should work with esnext targets

Use Cases

JS modules loaders for Node might not support importing CJS with import statements, so you would use require to import them. But we'd still like to bring in their types. This is what import assignment is designed for, it's just disallowed with esnext targets.

Examples

This:

import * as m from './a-module.js';
import cjs = require('some-cjs');

should emit:

import * as m from './a-module.js';
const cjs = require('some-cjs');

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript / JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. new expression-level syntax)

未指定任何文件或测试。首先跟踪 TypeScript 针对 esnext 目标的 import-assignment 处理，然后将当前输出与 issue 中的示例进行比较；当该赋值输出一个基于 require 的声明，同时保留现有的 import 时，工作就完成了。