Closed OCRG-Ohio closed 6 months ago
[02:43:22.827] Installing @sveltejs/adapter-vercel... [02:43:24.520] npm ERR! code ERESOLVE [02:43:24.523] npm ERR! ERESOLVE unable to resolve dependency tree [02:43:24.524] npm ERR! [02:43:24.524] npm ERR! While resolving: primo-server@2.0.0--beta.40 [02:43:24.524] npm ERR! Found: @sveltejs/kit@1.30.3 [02:43:24.525] npm ERR! node_modules/@sveltejs/kit [02:43:24.525] npm ERR! dev @sveltejs/kit@"^1.30.3" from the root project [02:43:24.525] npm ERR! [02:43:24.525] npm ERR! Could not resolve dependency: [02:43:24.525] npm ERR! peer @sveltejs/kit@"^2.0.0" from @sveltejs/adapter-vercel@4.0.3 [02:43:24.526] npm ERR! node_modules/@sveltejs/adapter-vercel [02:43:24.526] npm ERR! dev @sveltejs/adapter-vercel@"*" from the root project [02:43:24.526] npm ERR! [02:43:24.526] npm ERR! Fix the upstream dependency conflict, or retry [02:43:24.526] npm ERR! this command with --force, or --legacy-peer-deps [02:43:24.526] npm ERR! to accept an incorrect (and potentially broken) dependency resolution. [02:43:24.527] npm ERR! [02:43:24.527] npm ERR! See /vercel/.npm/eresolve-report.txt for a full report.
That should have been fixed with the latest update (see https://github.com/primocms/primo/issues/366). Did you sync your fork?
it is fixed. the issue should be closed
[02:43:22.827] Installing @sveltejs/adapter-vercel... [02:43:24.520] npm ERR! code ERESOLVE [02:43:24.523] npm ERR! ERESOLVE unable to resolve dependency tree [02:43:24.524] npm ERR! [02:43:24.524] npm ERR! While resolving: primo-server@2.0.0--beta.40 [02:43:24.524] npm ERR! Found: @sveltejs/kit@1.30.3 [02:43:24.525] npm ERR! node_modules/@sveltejs/kit [02:43:24.525] npm ERR! dev @sveltejs/kit@"^1.30.3" from the root project [02:43:24.525] npm ERR! [02:43:24.525] npm ERR! Could not resolve dependency: [02:43:24.525] npm ERR! peer @sveltejs/kit@"^2.0.0" from @sveltejs/adapter-vercel@4.0.3 [02:43:24.526] npm ERR! node_modules/@sveltejs/adapter-vercel [02:43:24.526] npm ERR! dev @sveltejs/adapter-vercel@"*" from the root project [02:43:24.526] npm ERR! [02:43:24.526] npm ERR! Fix the upstream dependency conflict, or retry [02:43:24.526] npm ERR! this command with --force, or --legacy-peer-deps [02:43:24.526] npm ERR! to accept an incorrect (and potentially broken) dependency resolution. [02:43:24.527] npm ERR! [02:43:24.527] npm ERR! See /vercel/.npm/eresolve-report.txt for a full report.