Microsoft/TypeScript

Allow `import.meta.url` when `module` is `node16` or `node18`

Open

#61,441 opened on Mar 17, 2025

View on GitHub
 (2 comments) (3 reactions) (0 assignees)TypeScript (6,726 forks)batch import
BugDomain: Node ESMHelp Wanted

Repository metrics

Stars
 (48,455 stars)
PR merge metrics
 (Avg merge 6d 17h) (9 merged PRs in 30d)

Description

🔎 Search Terms

import.meta' meta-property '--module' option 'es2020' 'es2022' 'esnext' 'system' 'node12' 'nodenext'

🕗 Version & Regression Information

  • This is the behavior in every version I tried, and I reviewed the FAQ for entries about the module option

⏯ Playground Link

https://www.typescriptlang.org/play/?moduleResolution=99&target=99&module=100&ts=5.8.2#code/MYewdgziA2CmB00QHMAUBLAtgBxAJwBd5NYCBDeAVz2gEoBuAWACgg

💻 Code

console.log(import.meta.url);

🙁 Actual behavior

When setting the module option to node16 or node18 you get the error message:

The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node12', or 'nodenext'.

🙂 Expected behavior

node16 and node18 should be supported. import.meta.url is available in those versions of Node and it makes no sense that this setting would say that it's available in Node 12 and the latest version of Node, but not the intermediate versions of Node.

Additional information about the issue

No response

Contributor guide

Research direction
Find the list of allowed module values for import.meta.url in the TypeScript source code. Likely in a checker or diagnostic file. Add 'node16' and 'node18' to that list.
Tech stack
typescript
Domain
compilersdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90