[lockfile-explorer] Lockfile explorer no longer works with latest version in non-rush repo
@octogonz is already working on this.
Since Oct 6, 2025.
Assessment
This issue has not been assessed yet.
Description
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 |
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 62
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoft/rushstack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100