Relative Content

Tag Archive for next.jsdeploymentvercel

Next.js Application error: a client-side exception has occurred (see the browser console for more information) error

I’ve deployed my Next.js project to Vercel. I’ve correctly set NEXT_PUBLIC_BACKEND_URL in the Environment Variables tab to fetch my data, but when I try to access the admin panel, I’m getting an “Application error: a client-side exception has occurred (see the browser console for more information).” When I check the console, I see a TypeError: Cannot read properties of undefined (reading ‘0’). Can you help me with this?
image 1
image 2

I am getting an ‘error occurred prerendering page’ & ‘location not found’ error while trying to deploy my Next.js project on Vercel

[**Deployment errors** `Error occurred prerendering page “/admin/categories”. ReferenceError: location is not defined at /vercel/path0/Frontend/.next/server/chunks/356.js:1:5918 at /vercel/path0/Frontend/.next/server/chunks/356.js:1:6692 at t.startTransition (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server /app-page.runtime.prod.js:12:108548) at Object.push (/vercel/path0/Frontend/.next/server/chunks/356.js:1:6680) at n (/vercel/path0/Frontend/.next/server/app/admin/system-users/page.js:1:2907) at nM (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server/ app- page.runtime.prod.js:12:47419) at nN (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server/ app-page.runtime.prod.js:12:64674) at nM (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server/ app-page.runtime.prod.js:12:59098) at nN (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server /app-page.runtime.prod.js:12:64674) at nI (/vercel/path0/Frontend/node_modules/next/dist/compiled/next-server /app-page.runtime.prod.js:12:46806)` here is my folder structure Folder structure My […]

How can I fix the npm ERR! ERESOLVE could not resolve, on Next.Js app while Vercel Deployment?

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! react@”^17.0.2″ from the root project
npm ERR! peer react@”>=0.14.0″ from @hypnosphi/[email protected]
npm ERR! node_modules/@hypnosphi/create-react-context
npm ERR! @hypnosphi/create-react-context@”^0.3.1″ from [email protected]
npm ERR! node_modules/react-popper
npm ERR! react-popper@”^1.3.6″ from [email protected]
npm ERR! node_modules/reactstrap
npm ERR! reactstrap@”^8.10.0″ from the root project
npm ERR! 6 more (framer-motion, react-dom, react-popper, …)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@”^18.2.0″ from [email protected]
npm ERR! node_modules/next
npm ERR! next@”^14.2.3″ from the root project
npm ERR! peer next@”>=10.2.0″ from [email protected]
npm ERR! node_modules/eslint-config-next
npm ERR! dev eslint-config-next@”11.1.2″ from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@”^18.2.0″ from [email protected]
npm ERR! node_modules/next
npm ERR! next@”^14.2.3″ from the root project
npm ERR! peer next@”>=10.2.0″ from [email protected]
npm ERR! node_modules/eslint-config-next
npm ERR! dev eslint-config-next@”11.1.2″ from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with –force or –legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /vercel/.npm/_logs/2024-05-18T21_30_09_535Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /vercel/.npm/_logs/2024-05-18T21_30_09_535Z-debug-0.log
Error: Command “npm install” exited with 1