microsoft / microsoft/TypeScript
"The inferred type of X cannot be named without a reference to Y" (TS2742) still happens, when working with npm link to link packages manually
@weswigham arbeitet bereits daran.
Seit 18.6.2024.
- Vorherrschende Sprache
- Go
- Sterne
- 111k
- Forks
- 14.4k
- Ø Merge
- 1 T. 19 Std.
- Gemergte PRs (30 T.)
- 117
Beschreibung
🔎 Search Terms
is:issue is:open 2742
🕗 Version & Regression Information
This seems to not be a regression bug
⏯ Playground Link
https://github.com/Teascade/typescript-error-demonstration
💻 Code
// In the example provided
// https://github.com/Teascade/typescript-error-demonstration
import { extended } from '@privateprefix/lib';
// src/index.ts(4,14): error TS2742: The inferred type of 'a' cannot be named without a reference to '@privateprefix/lib/node_modules/joi'. This is likely not portable. A type annotation is necessary.
export const a = extended.object().keys();
Replacing this with
// Joi is declared, but never used ts(6133)
import { type Joi, extended } from '@privateprefix/lib';
// This works now, though
export const a = extended.object().keys();
🙁 Actual behavior
Produces src/index.ts(4,14): error TS2742: The inferred type of 'a' cannot be named without a reference to '@privateprefix/lib/node_modules/joi'. This is likely not portable. A type annotation is necessary.
🙂 Expected behavior
No error is to be expected
Additional information about the issue
In https://github.com/microsoft/TypeScript/issues/42873#issuecomment-2066874644 it was mentioned, that this issue would now be resolved in TypeScript beta 5.5.0, but it seems to still be broken in this specific scenario
I've made a minimal repository to reroduce this issue in https://github.com/Teascade/typescript-error-demonstration
The GitHub repository has a github action in which the issue is reproduced: https://github.com/Teascade/typescript-error-demonstration/actions/runs/9568149578/job/26377636108
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.