monorepo

monorepo copied to clipboard

Getting following error when pnpm install

Scope: all 12 workspace projects

Lockfile is up to date, resolution step is skipped
Already up to date
apps/docs preinstall$ pnpm exec inherit -u
│ Nothing needs to be updated.
└─ Done in 507ms
apps/site preinstall$ pnpm exec inherit -u
│ Nothing needs to be updated.
└─ Done in 502ms
. preinstall$ pnpm exec inherit -u
│ Nothing needs to be updated.
└─ Done in 500ms
apps/+app preinstall$ pnpm exec inherit -u
│ Nothing needs to be updated.
└─ Done in 501ms
. postinstall$ pnpm exec ./.sh/symlinks.sh
└─ Running...
apps/+app prepare$ svelte-kit sync
│ file:///Users/weye/workspace/my-app/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@sveltejs/kit/src/exports/vite/d
│ import { isCSSRequest } from 'vite';
│          ^^^^^^^^^^^^
│ SyntaxError: The requested module 'vite' does not provide an export named 'isCSSRequest'
│     at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
│     at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
│     at async Promise.all (index 0)
│     at async ESMLoader.import (node:internal/modules/esm/loader:528:24)
│     at async load_config (file:///Users/weye/workspace/my-app/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@svelt
│     at async file:///Users/weye/workspace/my-app/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@sveltejs/kit/src/c
│ Node.js v18.8.0
└─ Failed in 199ms at /Users/weye/workspace/my-app/apps/+app
apps/site prepare$ svelte-kit sync
└─ Running...
apps/docs prepare$ svelte-kit sync
└─ Running...
 ELIFECYCLE  Command failed with exit code 1.

Updates are coming soon

What's so funny about this issue, Joseph?

Any update to this issue? I'm having the same problem.

Hi @oneezy - I managed to fix this by updated svelte and vite. However, I did this simply by updating every occurrences. I'm aware than some of these instances are derived / generated.

If you let me know where I should make this change I'll do a PR.

Thanks

Hi @oneezy - I got the same error and don't find a fix on Vite repo here : https://github.com/vitejs/vite/issues/11190