We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I installed lockfile-explorer and run it immediately.
Following docs here: https://github.com/microsoft/rushstack/tree/main/apps/lockfile-explorer
npm install -g @rushstack/lockfile-explorer lockfile-explorer
The second command fails.
Expected result:
Not throw error.
Actual result:
Outputs following and exits with non-zero code.
➜ tmp git:(macos) ✗ npm install -g @rushstack/lockfile-explorer changed 178 packages in 2s ➜ tmp git:(macos) ✗ lockfile-explorer node:internal/modules/cjs/loader:998 throw err; ^ Error: Cannot find module '@microsoft/rush-lib/lib/api/RushConfiguration' Require stack: - ~/.nvm/versions/node/v18.12.1/lib/node_modules/@rushstack/lockfile-explorer/lib/init.js - ~/.nvm/versions/node/v18.12.1/lib/node_modules/@rushstack/lockfile-explorer/lib/start.js - ~/.nvm/versions/node/v18.12.1/lib/node_modules/@rushstack/lockfile-explorer/bin/lockfile-explorer
Please answer these questions to help us investigate your issue more quickly:
@rushstack/lockfile-explorer
node -v
The text was updated successfully, but these errors were encountered:
This was fixed by #4697.
Sorry, something went wrong.
No branches or pull requests
Summary
I installed lockfile-explorer and run it immediately.
Repro steps
Following docs here: https://github.com/microsoft/rushstack/tree/main/apps/lockfile-explorer
The second command fails.
Expected result:
Not throw error.
Actual result:
Outputs following and exits with non-zero code.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@rushstack/lockfile-explorer
version?node -v
)?The text was updated successfully, but these errors were encountered: