prehistoric-hamburger-31861
08/20/2025, 4:46 AMpnpm install
with multiple packages, only one package gets installed but pnpm reports success. Subsequent pnpm install
commands report "Already up to date" despite missing packages.
To Reproduce
1. Run: pnpm install @livekit/components-react @livekit/components-styles livekit-client
2. Observe output shows only 1 package added instead of 3
3. Run pnpm install
again
4. Observe "Already up to date" message despite missing packages
Expected behavior
All 3 specified packages should be installed, or an error should be reported if installation fails.
Actual behavior
• Only @livekit/components-styles
was installed
• @livekit/components-react
and livekit-client
were not installed
• No error was reported
• Lockfile was updated as if all packages were installed
• Subsequent installs report "Already up to date"tall-airline-16756
08/20/2025, 4:47 AMtall-airline-16756
08/20/2025, 4:47 AMpackage.json
file or at least the part with the dependencies
• The version of pnpm
you’re working with
• Any custom setups you have in your .pnpmrc
file
• Whether you’ve tried adding autoInstallPeers: true
in your .pnpmrc
file
Having these details will really help us figure out if the problem is due to dependency conflicts or something specific in your project’s setup.
Sources: complex-agents/nova-sonic/nova-sonic-form-agent/pnpm-lock.yaml | pnpm-lock.yaml | client/web/pnpm-lock.yaml | pnpm-lock.yamlprehistoric-hamburger-31861
08/20/2025, 4:54 AMtall-airline-16756
08/20/2025, 4:55 AMpackage.json
and the issue you mentioned, here are some friendly steps to help you troubleshoot the installation problem:
1. Clear the package manager cache:
pnpm store prune
rm -rf node_modules
rm pnpm-lock.yaml
pnpm install
2. Verify Node.js version: Just double-check that you’re running Node.js 18 or higher, since LiveKit packages need that.
3. Check peer dependencies: Try running pnpm install --shamefully-hoist
— this often fixes peer dependency hiccups. Or you can manually add any missing ones if you spot them.
4. Use exact versions: Instead of using version ranges like ^2.9.9
, specifying exact versions for LiveKit packages can help avoid any conflicts.
5. Address network or registry issues: If you think network troubles might be the culprit, give this a shot:
pnpm config set registry <https://registry.npmjs.org/>
pnpm install --network-timeout 300000
Hopefully, these tips get things working smoothly! If you run into any more issues or see specific error messages, just let me know — I’m here to help.
Sources: package.json | complex-agents/role-playing/role_playing_frontend/pnpm-lock.yaml