Unable to resolve dependency tree - svelte

[MiXeR54]

Are there any recommendations on how to solve this one?

npm error Found: [email protected]
npm error node_modules/svelte
npm error   peer svelte@"^4.0.0 || ^5.0.0-next.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     peerOptional @sveltejs/kit@"^1 || ^2" from @vercel/[email protected]
npm error     node_modules/@vercel/speed-insights
npm error       @vercel/speed-insights@"1.0.12" from the root project
npm error   peer svelte@"^5.0.0-next.96 || ^5.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/vite-plugin-svelte
npm error     peer @sveltejs/vite-plugin-svelte@"^3.0.0 || ^4.0.0-next.1" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/kit
npm error       peerOptional @sveltejs/kit@"^1 || ^2" from @vercel/[email protected]
npm error       node_modules/@vercel/speed-insights
npm error         @vercel/speed-insights@"1.0.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional svelte@"^4" from @vercel/[email protected]
npm error node_modules/@vercel/speed-insights
npm error   @vercel/speed-insights@"1.0.12" from the root project

My dependencies:

"dependencies": {
"@auth/prisma-adapter": "2.7.2",
"@fortawesome/fontawesome-svg-core": "6.6.0",
"@fortawesome/free-brands-svg-icons": "6.6.0",
"@fortawesome/free-regular-svg-icons": "6.6.0",
"@fortawesome/free-solid-svg-icons": "6.6.0",
"@fortawesome/react-fontawesome": "0.2.2",
"@hookform/resolvers": "3.9.0",
"@prisma/client": "5.21.1",
"@radix-ui/react-accordion": "1.2.1",
"@radix-ui/react-alert-dialog": "1.1.2",
"@radix-ui/react-checkbox": "1.1.2",
"@radix-ui/react-dialog": "1.1.2",
"@radix-ui/react-dropdown-menu": "2.1.2",
"@radix-ui/react-label": "2.1.0",
"@radix-ui/react-scroll-area": "1.2.0",
"@radix-ui/react-select": "2.1.2",
"@radix-ui/react-separator": "1.1.0",
"@radix-ui/react-slot": "1.1.0",
"@radix-ui/react-tabs": "1.1.1",
"@radix-ui/react-tooltip": "1.1.3",
"@sanity/document-internationalization": "3.1.0",
"@sanity/react-loader": "1.10.7",
"@sanity/vision": "3.61.0",
"@sentry/nextjs": "8.34.0",
"@tanstack/react-query": "5.59.15",
"@tanstack/react-query-devtools": "5.59.15",
"@tanstack/react-table": "8.20.5",
"@vercel/analytics": "1.3.1",
"@vercel/speed-insights": "1.0.12",
"axios": "1.7.7",
"class-variance-authority": "0.7.0",
"clsx": "2.1.1",
"cmdk": "1.0.0",
"date-fns": "4.1.0",
"embla-carousel-react": "8.3.0",
"lucide-react": "0.453.0",
"next": "14.2.15",
"next-auth": "4.24.8",
"next-intl": "3.21.1",
"next-sanity": "9.5.5",
"next-themes": "0.3.0",
"react": "18.3.1",
"react-country-flag": "3.1.0",
"react-dom": "18.3.1",
"react-hook-form": "7.53.1",
"recharts": "2.13.0",
"sharp": "0.33.5",
"sonner": "1.5.0",
"tailwind-merge": "2.5.4",
"zod": "3.23.8"
},
"devDependencies": {
"@tailwindcss/typography": "0.5.15",
"@types/node": "22.7.7",
"@types/react": "18.3.11",
"@types/react-dom": "18.3.1",
"@typescript-eslint/eslint-plugin": "8.10.0",
"@typescript-eslint/parser": "8.10.0",
"autoprefixer": "10.4.20",
"eslint": "8.57.0",
"eslint-config-next": "14.2.15",
"eslint-config-prettier": "9.1.0",
"eslint-plugin-prettier": "5.2.1",
"eslint-plugin-simple-import-sort": "12.1.1",
"knip": "5.33.3",
"local-ssl-proxy": "2.0.5",
"postcss": "8.4.47",
"prettier": "3.3.3",
"prettier-eslint": "16.3.0",
"prettier-plugin-tailwindcss": "0.6.8",
"prisma": "5.21.1",
"tailwindcss": "3.4.14",
"tailwindcss-animate": "1.0.7",
"typescript": "5.6.3"
}

[mambucodev]

I'm having this issue too. in my case @vercel/speed-insights requires an older version of svelte, while nextjs requires a newer one.

[pauljones0]

Good to know I'm not the only one with this issue. Seems wrong to install with

npm install @vercel/speed-insights --legacy-peer-deps

[jeevenmotion]

Having same issue

[gorchov]

Same problem trying to install npm i @vercel/speed-insights in my new next 14.2.15 app

[skve]

I made a PR (#78) to upgrade to Svelte 5 which should fix it.

[jeevenmotion]

Hopefully it gets merged sometime soon?
@feugy @tobiaslins

[swarnava]

Hi,

Swarnava from Vercel team here. Our team is currently looking into this.

[swarnava]

@vercel/[email protected] is released which should fix the problem.