next-basic-blog icon indicating copy to clipboard operation
next-basic-blog copied to clipboard

build failed

Open ymbrite opened this issue 3 weeks ago • 1 comments

hi.

i changed next's value and react's value to latest and ^18.2.0 respectively in package.json, and i set dependencies installation command to be 'npm install --force', then click the deploy button,it shows:

23:52:52.448 Running build in Washington, D.C., USA (East) – iad1 23:52:52.449 Build machine configuration: 2 cores, 8 GB 23:52:52.573 Cloning github.com/ymbrite/nbb (Branch: master, Commit: 377729e) 23:52:52.574 Previous build caches not available. 23:52:52.803 Cloning completed: 230.000ms 23:52:55.518 Running "vercel build" 23:52:56.247 Vercel CLI 50.1.3 23:52:56.585 Running "install" command: npm install --force... 23:52:56.858 npm warn using --force Recommended protections disabled. 23:53:06.835 npm warn ERESOLVE overriding peer dependency 23:53:06.836 npm warn While resolving: [email protected] 23:53:06.837 npm warn Found: [email protected] 23:53:06.837 npm warn node_modules/react-dom 23:53:06.837 npm warn react-dom@"^16.13.0" from the root project 23:53:06.838 npm warn 1 more (react-highlight) 23:53:06.838 npm warn 23:53:06.838 npm warn Could not resolve dependency: 23:53:06.839 npm warn peer react-dom@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from [email protected] 23:53:06.839 npm warn node_modules/next 23:53:06.839 npm warn next@"latest" from the root project 23:53:06.839 npm warn 23:53:06.840 npm warn Conflicting peer dependency: [email protected] 23:53:06.840 npm warn node_modules/react-dom 23:53:06.842 npm warn peer react-dom@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from [email protected] 23:53:06.842 npm warn node_modules/next 23:53:06.842 npm warn next@"latest" from the root project 23:53:10.249 npm warn ERESOLVE overriding peer dependency 23:53:10.250 npm warn While resolving: [email protected] 23:53:10.250 npm warn Found: [email protected] 23:53:10.250 npm warn node_modules/react 23:53:10.251 npm warn react@"^18.2.0" from the root project 23:53:10.251 npm warn 2 more (next, styled-jsx) 23:53:10.251 npm warn 23:53:10.251 npm warn Could not resolve dependency: 23:53:10.251 npm warn peer react@"^16.14.0" from [email protected] 23:53:10.251 npm warn node_modules/react-dom 23:53:10.252 npm warn react-dom@"^16.13.0" from the root project 23:53:10.252 npm warn 1 more (react-highlight) 23:53:10.252 npm warn 23:53:10.252 npm warn Conflicting peer dependency: [email protected] 23:53:10.252 npm warn node_modules/react 23:53:10.253 npm warn peer react@"^16.14.0" from [email protected] 23:53:10.253 npm warn node_modules/react-dom 23:53:10.254 npm warn react-dom@"^16.13.0" from the root project 23:53:10.254 npm warn 1 more (react-highlight) 23:53:10.296 npm warn ERESOLVE overriding peer dependency 23:53:10.297 npm warn While resolving: [email protected] 23:53:10.297 npm warn Found: [email protected] 23:53:10.297 npm warn node_modules/react 23:53:10.298 npm warn react@"^18.2.0" from the root project 23:53:10.298 npm warn 2 more (next, styled-jsx) 23:53:10.298 npm warn 23:53:10.298 npm warn Could not resolve dependency: 23:53:10.298 npm warn peer react@"^15.0.0 || ^16.0.0" from [email protected] 23:53:10.298 npm warn node_modules/react-highlight 23:53:10.299 npm warn react-highlight@"^0.12.0" from the root project 23:53:10.299 npm warn 23:53:10.299 npm warn Conflicting peer dependency: [email protected] 23:53:10.299 npm warn node_modules/react 23:53:10.299 npm warn peer react@"^15.0.0 || ^16.0.0" from [email protected] 23:53:10.300 npm warn node_modules/react-highlight 23:53:10.300 npm warn react-highlight@"^0.12.0" from the root project 23:53:10.306 npm warn ERESOLVE overriding peer dependency 23:53:10.307 npm warn While resolving: [email protected] 23:53:10.307 npm warn Found: [email protected] 23:53:10.307 npm warn node_modules/react 23:53:10.307 npm warn react@"^18.2.0" from the root project 23:53:10.307 npm warn 2 more (next, styled-jsx) 23:53:10.307 npm warn 23:53:10.307 npm warn Could not resolve dependency: 23:53:10.309 npm warn peer react@"^15.0.0 || ^16.0.0" from [email protected] 23:53:10.311 npm warn node_modules/react-markdown 23:53:10.312 npm warn react-markdown@"^4.3.1" from the root project 23:53:10.312 npm warn 23:53:10.312 npm warn Conflicting peer dependency: [email protected] 23:53:10.312 npm warn node_modules/react 23:53:10.312 npm warn peer react@"^15.0.0 || ^16.0.0" from [email protected] 23:53:10.312 npm warn node_modules/react-markdown 23:53:10.313 npm warn react-markdown@"^4.3.1" from the root project 23:53:13.836 npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. 23:53:13.917 npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported 23:53:13.918 npm warn deprecated [email protected]: Use String.prototype.trim() instead 23:53:14.008 npm warn deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash. 23:53:14.688 npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported 23:53:15.060 npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead 23:53:15.312 npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead 23:53:18.039 npm warn deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest 23:53:18.266 npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. 23:53:22.504 23:53:22.504 added 439 packages, and audited 440 packages in 26s 23:53:22.505 23:53:22.505 61 packages are looking for funding 23:53:22.505 run npm fund for details 23:53:22.620 23:53:22.620 49 vulnerabilities (46 moderate, 3 high) 23:53:22.620 23:53:22.621 To address issues that do not require attention, run: 23:53:22.621 npm audit fix 23:53:22.621 23:53:22.621 To address all issues (including breaking changes), run: 23:53:22.621 npm audit fix --force 23:53:22.621 23:53:22.621 Run npm audit for details. 23:53:22.678 Detected Next.js version: 16.1.1 23:53:22.679 Running "npm run build" 23:53:22.779 23:53:22.779 > [email protected] build 23:53:22.779 > next build 23:53:22.779 23:53:23.356 Attention: Next.js now collects completely anonymous telemetry regarding usage. 23:53:23.357 This information is used to shape Next.js' roadmap and prioritize features. 23:53:23.357 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: 23:53:23.357 https://nextjs.org/telemetry 23:53:23.357 23:53:23.372 ▲ Next.js 16.1.1 (Turbopack) 23:53:23.373 23:53:23.399 Running TypeScript ... 23:53:23.463 Creating an optimized production build ... 23:53:30.113 23:53:30.113 > Build error occurred 23:53:30.116 Error: Turbopack build failed with 1 errors: 23:53:30.116 ./node_modules/next/dist/client/index.js:40:58 23:53:30.116 Module not found: Can't resolve 'react-dom/client' 23:53:30.116 Import map: aliased to module 'react-dom' with subpath '/client' inside of [project]/ 23:53:30.116 23:53:30.116 23:53:30.116 Import trace: 23:53:30.116 Browser: 23:53:30.116 ./node_modules/next/dist/client/index.js 23:53:30.116 ./node_modules/next/dist/client/next-turbopack.js 23:53:30.116 23:53:30.116 https://nextjs.org/docs/messages/module-not-found 23:53:30.116 23:53:30.117 23:53:30.117 at (https://nextjs.org/docs/messages/module-not-found) 23:53:30.161 Error: Command "npm run build" exited with 1

how to fix the errors? tks a lot!

ymbrite avatar Jan 05 '26 07:01 ymbrite