Playground typing issue

Nessuno ha ancora preso questa issue.

### 🔎 Search Terms

TypeScript Playground error when attempting to import something from `@octokit/core/types`

### 🕗 Version & Regression Information

Seems irrelavent to TS version

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAKjgQwM5wPIGMYQNbAwAqAnmAKboBmUEIcA5AAIQ76ED0W05HMZlBgCghoSLDgBvTGwLwAvnBp1GrXHIYBuEdwB2qeAHNCACwCuAIzgBeOLvIB3GesIAKAJTah5AB7j4egbO7MQCqF6+-nD8FMFypLG2MeQQVHDGMOYW2kA

### 💻 Code

```ts
import * as OctokitTypes from '@octokit/core/types';
```

### 🙁 Actual behavior

**Behavior 1**:

Type of the following variable is recognized as `any`:
```ts
import { Octokit } from 'octokit';
export type T = typeof Octokit;
```

**Behavior 2**:

Type of the following variable is recognized as `any`;
```ts
import * as OctokitTypes from '@octokit/core/types';
export const OctokitTypes;
```

**Behavior 3**: _Even stranger behavior_

In the following code snippet:
```ts
import * as OctokitTypes from '@octokit/core/types';
```

1. Remove any character from package name `@octokit/core/types` (e.g. `@octokit/core/type`), TS error occured, which is expected

2. Re-add the removed character, TS error remained, which is very weird

Apparently there is some problem with the language server, as the package name has been changed to `*/types`, but it still reports error of `*/type`

### 🙂 Expected behavior

N/A

### Additional information about the issue

_No response_

Inizia riproducendo i tre comportamenti nel TypeScript Playground collegato, concentrandoti sull’import di @octokit/core/types e sulla diagnostica obsoleta dopo la modifica del nome del pacchetto. Traccia il comportamento rilevante della risoluzione dei moduli o del language server; il lavoro è completato quando l’import valido viene risolto con i suoi tipi effettivi e la diagnostica viene aggiornata dopo la modifica.

Scritto dal modello di indicizzazione a partire dal testo della issue.