[BUG] npm dependency issue
pureair opened this issue · comments
npm dependency issue on vitest
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Follow the Installation Guide https://unsaged.com/docs/getting-started/installation
- When running "npm i" in ~/unSAGED/apps/unsaged, error reported as follow
# npm resolution error report
While resolving: unsaged@0.0.1
Found: vitest@1.0.4
node_modules/vitest
dev vitest@"^1.0.4" from unsaged@0.0.1
apps/unsaged
unsaged@0.0.1
node_modules/unsaged
workspace apps/unsaged from the root project
peer vitest@"^1.0.0" from @vitest/browser@1.0.4
node_modules/@vitest/browser
peerOptional @vitest/browser@"^1.0.0" from vitest@1.0.4
peer vitest@"^1.0.0" from @vitest/ui@1.0.4
node_modules/@vitest/ui
peerOptional @vitest/ui@"^1.0.0" from vitest@1.0.4
Could not resolve dependency:
peer vitest@">=0.30.0 <1" from @vitest/coverage-c8@0.33.0
node_modules/@vitest/coverage-c8
dev @vitest/coverage-c8@"^0.33.0" from unsaged@0.0.1
apps/unsaged
unsaged@0.0.1
node_modules/unsaged
workspace apps/unsaged from the root project
Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
Screenshots
Desktop (please complete the following information):
- OS: Debian 12
Additional context
Running "docker build -t unsaged -f apps/unsaged/Dockerfile . --rm" in ~/unSAGED hung as well.
You will have to use pnpm instead of npm then it should work fine, I will update the docs to reflect this step correctly.
