TS1479 Unable to import types from ESM package when moduleResolution is nodenext

[trusktr]

Bug Report

When I set moduleResolution: "nodenext" I see this error when I try to import type from a package:

Then I tried to switch to dynamic import() (even in for a type, not a runtime value), and get the same error:

With runtime value, we can typically switch to dynamic import() to get around the problem. But with type imports, this is not getting around the problem.

Here's the error message for searchability:

error message (click to open)

The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("wazum")' call instead.
  To convert this file to an ECMAScript module, change its file extension to '.mts', or add the field `"type": "module"` to '/Users/trusktr/src/project/package.json'.ts(1479)

Note that the error says

Consider writing a dynamic 'import("wazum")' call instead.

which is what I've done with import('wazum').Add.

Adding typeof has the same issue:

Note, the wazum package is not the one currently at https://npmjs.com/wazum, but the one installed from my current GitHub fork:

npm install 'wazum@trusktr/wazum#simple-esm-dist-output'

🔎 Search Terms

typescript moduleResolution nodenext unable to import types

🕗 Version & Regression Information

Not sure when it regressed, if at all.

⏯ Playground Link

I am unable to provide a playground link because it doesn't seem to be configurable with the required options.

TODO: make a clonable reproduction.

💻 Code

type t = import('wazum').Add // error ts(1479)

Here's my tsconfig:

{
	"compilerOptions": {
		// Compiler setup
		"target": "esnext",
		"module": "commonjs",
		"lib": ["ESNext"],
		"sourceMap": true,
		"outDir": "out",
		"moduleResolution": "nodenext",
		"esModuleInterop": true,
		"skipLibCheck": true,
		"forceConsistentCasingInFileNames": true,

		// Type checking
		"strict": true,
		"noUnusedLocals": true,
		"noImplicitReturns": true,
		"noImplicitOverride": true
	},
	"include": ["src/**/*.ts"],
	"exclude": ["out", "node_modules"]
}

🙁 Actual behavior

Unable to import types.

🙂 Expected behavior

Expect there to be some way to import types. import type imports are not regular ES Module imports, so it seems like import type {...} from '...' should just work, however I understand if it should match with the runtime import() requirement for CommonJS output for consistency, but that's just not working either.

Plus using dynamic import() syntax for type imports is too cumbersome because some features are missing, f.e. the ability to import generic types:

So even if import() is what I should be doing (currently not working) import type would be better.

[trusktr]

A simple workaround for now is to put a // @ts-expect-error comment over the import:

// @ts-expect-error moduleResolution:nodenext issue 54523
import type {SomeType} from 'some-lib'

[fatcerberus]

Known issue, see #52529. @ts-ignore/@ts-expect-error is the only current workaround.

[bmeck]

Seeing this as well after updating TS, workaround doesn't work as the type is still seen as non-existent.

[andrewbranch]

I think you can add the resolution-mode import assertion and ts-ignore the error that tells you not to do that.

import type { SomeType } from 'some-lib' assert { "resolution-mode": "module" }

This will become an import attribute and not illegal once we land support for import attributes.

[typescript-bot]

This issue has been marked as 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

[TheNoim]

import type { SomeType } from 'some-lib' assert { "resolution-mode": "module" }

This is currently the correct way I guess:

import type { SomeType } from 'some-lib' with { 'resolution-mode': 'import' };