`rstack/types/index.d.ts` references `@rsbuild/core/types` which cannot be resolved under pnpm
@chenjiahan ya está trabajando en esto.
Desde el 24/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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 directdependenciesentry of therstackpackage 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.0as the sole Rstack-related dependency in a pnpm project. - Open any file that pulls in
rstack/types(or opennode_modules/rstack/types/index.d.tsdirectly). - Observe the unresolved reference error on the
/// <reference types="@rsbuild/core/types" />line.
Notes
rs lib(build) completes successfully and generates valid declaration files viatsgo, 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_modulesstructure and TypeScript's triple-slash reference resolution algorithm, which does not follow the same resolution rules as ordinaryimportresolution.
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 28
- Forks
- 1
- Merge medio
- 6 h 1 min
- PR fusionados (30 d)
- 101
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de rstackjs/rstack-cli
-
rstackjs/rstack-cli#518 · 1 asignado ·
-
Rstack CLI Roadmap Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
rstackjs/rstack-cli#44 ·
-
Dependency Dashboard Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
rstackjs/rstack-cli#37 ·
Todos los issues de rstackjs/rstack-cli
Issues similares
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Crush Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
ElementsProject/cln-application#167 · 1 comentario · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Quantco/pnpm-licenses#17 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100