`rstack/types/index.d.ts` references `@rsbuild/core/types` which cannot be resolved under pnpm

Offen

#519 erstellt am 24.9.2026 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@chenjiahan arbeitet bereits daran.

Seit 24.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Environment

rstack: 0.8.0
Package manager: pnpm (strict node_modules)
Editor: VS Code

Summary

rstack/types/index.d.ts contains:

/// <reference types="@rsbuild/core/types" />

This reference fails to resolve in the editor (VS Code / tsserver), producing a red squiggly / unresolved reference error, even though:

@rsbuild/core (~2.2.8) is declared as a direct dependencies entry of the rstack package itself
The file physically exists at node_modules/.pnpm/rstack@0.8.0_..._typescript@7.0.2/node_modules/@rsbuild/core/types.d.ts

Steps to reproduce

Install rstack@0.8.0 as the sole Rstack-related dependency in a pnpm project.
Open any file that pulls in rstack/types (or open node_modules/rstack/types/index.d.ts directly).
Observe the unresolved reference error on the /// <reference types="@rsbuild/core/types" /> line.

Notes

rs lib (build) completes successfully and generates valid declaration files via tsgo, suggesting the build-time module resolution differs from the editor's (tsserver's) resolution of the same triple-slash reference.
This may be a known friction point between pnpm's isolated node_modules structure and TypeScript's triple-slash reference resolution algorithm, which does not follow the same resolution rules as ordinary import resolution.

Suggested fix

Given that rstack already re-exports APIs from its dependencies via subpaths (rstack/app, rstack/lib, rstack/lint), consider having rstack/types similarly re-export or inline the relevant @rsbuild/core type definitions rather than relying on a raw external triple-slash reference, for consistency with the rest of the package's re-export design.

Vorherrschende Sprache: TypeScript
Sterne: 28
Forks: 1
Ø Merge: 6 Std. 1 Min.
Gemergte PRs (30 T.): 101

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus rstackjs/rstack-cli

`rs` command collides with the pre-installed BSD rs (reshape) utility on macOS/BSD, causing a silent, CPU-idle hang Offen

rstackjs/rstack-cli#518 · 1 zugewiesene Person · Erstellt am 24.9.2026
Rstack CLI Roadmap Offen

Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 20/100

rstackjs/rstack-cli#44 · Erstellt am 16.7.2026
Dependency Dashboard Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100

rstackjs/rstack-cli#37 · Erstellt am 14.7.2026

Alle Issues in rstackjs/rstack-cli