Bug: settings in `tsconfig.json#paths` and `package.json#imports` conflicts · Microsoft/TypeScript#60821

Repository-Metriken

Stars: (48.455 Stars)
PR-Merge-Metriken: (Durchschn. Merge 6T 17h) (9 gemergte PRs in 30 T)

Beschreibung

🔎 Search Terms

"package.json imports path"

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about this issue

⏯ Playground Link

No response

💻 Code

My repository is intended to reproduce a bug that manifests when the following three settings are combined:

"rootDir": "." in the tsconfig.json file, which is required only for VS Code and eslint.config.mjs;
paths in the tsconfig.json file creates an alias for the path #lib/*, pointing to ./src/*;
imports in the package.json file creates an alias for the path #lib/*, pointing to ./dist/*.

In such cases, TypeScript suggestions merge content from both the ./dist/* and ./src/* directories:

🙁 Actual behavior

As you can see, file1.js, file2.js, and index.js appear at the same level as the src and test folders, which is incorrect.

🙂 Expected behavior

The setting described in point 2 should take higher precedence for TypeScript over the setting in point 3.
In any case, the settings in points 2 and 3 should not be merged.

Additional information about the issue

If in point 1 the setting is changed to "rootDir": "src", the bug disappears. However, in this case, you cannot use "include": ["test"] in the tsconfig.json file, which is very inconvenient. Instead, it is more practical to use the "rootDir": "src" setting in the tsconfig.build.json file.

Contributor Guide

Research-Richtung: Untersuche die Interaktion zwischen tsconfig.json Pfaden und package.json Imports im TypeScript Compiler. Der Meldende stellt ein Reproduktions Repository unter https://github.com/KostyaTretyak/package json imports bug bereit. Beginnen Sie damit, zu prüfen, wie TypeScript Modulaliase auflöst, wenn sowohl `paths` als auch `imports` definiert sind, mit Fokus auf die Zusammenführungslogik. Das erwartete Verhalten ist, dass `paths` Vorrang vor `imports` haben sollte. Sehen Sie sich den Modulauflösungscode des Compilers an, wahrscheinlich in `src/services/` oder `src/compiler/`, und erwägen Sie, einen Testfall hinzuzufügen, um Regressionen zu verhindern.
Tech Stack: typescriptjavascript
Domain: toolingbuild system
Issue Type: Fehler
Schwierigkeit: 3
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: TypeScriptNode.js
Einsteigerfreundlichkeit: 50