[lockfile-explorer] Lockfile explorer no longer works with latest version in non-rush repo
@octogonz ya está trabajando en esto.
Desde el 6/10/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Summary
We use lockfile-explorer as a tool for analyzing our pnpm lockfile. It's awesome! Something seem to have broke with the latest major upgrade of the tool.
Repro steps
- Install the latest lockfile explorer globally
- Run
lockfile-explorerin a directory containedpnpm-lock.yaml
Expected result:
Should work similar to how it worked with v1.7.42
Actual result:
Rush Lockfile Explorer 2.0.1 - https://lfx.rushstack.io/
App launched on http://localhost:8091
/Users/schaap/.local/share/fnm/node-versions/v18.18.2/installation/lib/node_modules/@rushstack/lockfile-explorer/lib/graph/lockfilePath.js:87
throw new Error('getAbsolutePath(): relativePath goes above the root folder');
^
Error: getAbsolutePath(): relativePath goes above the root folder
at Object.getAbsolute (/Users/schaap/.local/share/fnm/node-versions/v18.18.2/installation/lib/node_modules/@rushstack/lockfile-explorer/lib/graph/lockfilePath.js:87:23)
at createProjectLockfileEntry (/Users/schaap/.local/share/fnm/node-versions/v18.18.2/installation/lib/node_modules/@rushstack/lockfile-explorer/lib/graph/lfxGraphLoader.js:214:49)
at Object.generateLockfileGraph (/Users/schaap/.local/share/fnm/node-versions/v18.18.2/installation/lib/node_modules/@rushstack/lockfile-explorer/lib/graph/lfxGraphLoader.js:389:30)
at /Users/schaap/.local/share/fnm/node-versions/v18.18.2/installation/lib/node_modules/@rushstack/lockfile-explorer/lib/cli/explorer/ExplorerCommandLineParser.js:155:42
Node.js v18.18.2
Details
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@rushstack/lockfile-explorer version? |
2.0.1 |
| Operating system? | Mac |
| Would you consider contributing a PR? | No |
Node.js version (node -v)? |
v18.18.2 |
- Lenguaje dominante
- TypeScript
- Estrellas
- 6.5k
- Forks
- 708
- Merge medio
- 4 d 13 h
- PR fusionados (30 d)
- 62
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 microsoft/rushstack
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de microsoft/rushstack
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100