Describe the bug When running `pnpm install` with ...
# ask-ai
p
Describe the bug When running
pnpm 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"
t
Thanks for reaching out, Mamlesh. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
To get to the bottom of this, could you share a few things with me? • Your
package.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.yaml
p
package.json { "name": "agent-starter-react", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev --turbopack", "build": "next build", "start": "next start", "lint": "next lint", "format": "prettier --write .", "format:check": "prettier --check ." }, "dependencies": { "@alert-easter-19258/components-react": "^2.9.9", "@phosphor-icons/react": "^2.1.8", "@radix-ui/react-context": "^1.1.2", "@radix-ui/react-direction": "^1.1.1", "@radix-ui/react-dismissable-layer": "^1.1.10", "@radix-ui/react-focus-guards": "^1.1.2", "@radix-ui/react-focus-scope": "^1.1.7", "@radix-ui/react-id": "^1.1.1", "@radix-ui/react-label": "^2.1.7", "@radix-ui/react-portal": "^1.1.9", "@radix-ui/react-primitive": "^2.1.3", "@radix-ui/react-scroll-area": "^1.2.9", "@radix-ui/react-select": "^2.2.5", "@radix-ui/react-slot": "^1.2.3", "@radix-ui/react-toggle": "^1.1.9", "@radix-ui/react-toolbar": "^1.1.10", "@radix-ui/react-use-controllable-state": "^1.2.2", "@radix-ui/react-use-layout-effect": "^1.1.1", "@radix-ui/react-use-previous": "^1.1.1", "@radix-ui/react-visually-hidden": "^1.2.3", "buffer-image-size": "^0.6.4", "class-variance-authority": "^0.7.1", "clsx": "^2.1.1", "livekit-client": "^2.13.3", "livekit-server-sdk": "^2.13.0", "mime": "^4.0.7", "motion": "^12.16.0", "next": "15.4.5", "next-themes": "^0.4.6", "react": "^19.0.0", "react-dom": "^19.0.0", "sonner": "^2.0.3", "tailwind-merge": "^3.3.0" }, "devDependencies": { "@eslint/eslintrc": "^3", "@tailwindcss/postcss": "^4", "@trivago/prettier-plugin-sort-imports": "^5.2.2", "@types/node": "^22.0.0", "@types/react": "^19", "@types/react-dom": "^19", "eslint": "^9", "eslint-config-next": "15.4.5", "eslint-config-prettier": "^10.1.5", "eslint-plugin-import": "^2.31.0", "eslint-plugin-prettier": "^5.5.0", "prettier": "^3.4.2", "prettier-plugin-tailwindcss": "^0.6.11", "tailwindcss": "^4", "tw-animate-css": "^1.3.0", "typescript": "^5" }, "packageManager": "pnpm@9.15.9" } Pnpm version: 9.15.9 I did not add any .pnpmrc file
t
Hey there! Looking at your
package.json
and the issue you mentioned, here are some friendly steps to help you troubleshoot the installation problem: 1. Clear the package manager cache:
Copy code
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:
Copy code
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