New chat started from template Lawn Maintenance Website
An error occurred during deployment. Please fix:
Resolving dependencies
Resolved, downloaded and extracted [1062]
Saved lockfile
$ next build
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSKmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSumu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSOmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSymu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS2mu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTVOmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTUGmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSCmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSGmu0SC55K5gw.woff2 failed, reason:
Retrying 1/3...
request to https://fonts.gstatic.com/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2 failed, reason:
Retrying 1/3...
Error: Could not find the module "/vercel/path1/node_modules/framer-motion/dist/es/index.mjs#motion#div" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at eb (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:136574)
at ek (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140197)
at Array.toJSON (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135626)
at stringify (<anonymous>)
at eP (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142090)
at eE (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142569)
at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
at Timeout._onTimeout (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:150268)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7) {
digest: '113954304'
}
Error: Could not find the module "/vercel/path1/node_modules/framer-motion/dist/es/index.mjs#motion#div" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at eb (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:136574)
at ek (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140197)
at Array.toJSON (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135626)
at stringify (<anonymous>)
at eP (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142090)
at eE (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142569)
at Timeout._onTimeout (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135346)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7) {
digest: '607843182'
}
Error: Could not find the module "/vercel/path1/node_modules/framer-motion/dist/es/index.mjs#motion#div" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at eb (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:136574)
at ek (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140197)
at Array.toJSON (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135626)
at stringify (<anonymous>)
at eP (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142090)
at eE (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142569)
at Timeout._onTimeout (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135346)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7) {
digest: '607843182'
}
Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Could not find the module "/vercel/path1/node_modules/framer-motion/dist/es/index.mjs#motion#div" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at eb (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:136574)
at ek (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140197)
at Array.toJSON (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135626)
at stringify (<anonymous>)
at eP (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142090)
at eE (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142569)
at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
at Timeout._onTimeout (/vercel/path1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:150268)
at listOnTimeout (node:internal/timers:594:17)
at process.processTimers (node:internal/timers:529:7)
> Export encountered errors on following paths:
/page: /
error: script "build" exited with code 1
Error: Command "bun run build" exited with 1
I apologize for the error. It seems the issue is related to the use of framer-motion
in a server component. Let's fix this by moving the framer-motion
animations to a client component. We'll update the Hero
component to resolve this issue.
These modifications should fix the deployment error by ensuring that framer-motion
is only used in client components. The rest of the application structure remains the same, maintaining the benefits of server-side rendering where possible.