Next.js部署Netlify遇exit code 1错误,求解决方案
Next.js部署到Netlify时构建失败(exit code 1)的解决方案
我尝试将基于Next.js的站点部署到Netlify,但持续出现构建失败错误(exit code 1)。此前站点可正常构建运行,目前已尝试重新上传站点、在构建部署设置中添加CI= npm run build,但问题仍未解决。具体报错日志如下:
3:43:14 PM: - info Generating static pages (2/6) 3:43:14 PM: - info Generating static pages (4/6) 3:43:14 PM: - info Generating static pages (6/6) 3:43:14 PM: > Export encountered errors on following paths: 3:43:14 PM: /account/page: /account 3:43:14 PM: 3:43:14 PM: build.command failed 3:43:14 PM: ──────────────────────────────────────────────────────────────── 3:43:14 PM: 3:43:14 PM: Error message 3:43:14 PM: Command failed with exit code 1: next build 3:43:14 PM: 3:43:14 PM: Error location 3:43:14 PM: In Build command from Netlify app: 3:43:14 PM: next build 3:43:14 PM: 3:43:14 PM: Resolved config 3:43:14 PM: build: 3:43:14 PM: command: next build 3:43:14 PM: commandOrigin: ui 3:43:14 PM: environment: 3:43:14 PM: - NEXT_PRIVATE_TARGET 3:43:14 PM: publish: /opt/build/repo/.next 3:43:14 PM: publishOrigin: ui 3:43:14 PM: plugins: 3:43:14 PM: - inputs: {} 3:43:14 PM: origin: ui 3:43:14 PM: package: '@netlify/plugin-nextjs' 3:43:16 PM: Build failed due to a user error: Build script returned non-zero exit code: 2 3:43:16 PM: Failing build: Failed to build site 3:43:17 PM: Finished processing build request in 43.454s
排查与解决步骤
- 聚焦/account页面的错误:日志明确指向该页面静态生成失败,优先检查:
- 页面是否使用了客户端专属API(如
window、document)但未做环境判断,用typeof window !== 'undefined'包裹相关代码,或移至useEffect中执行。 - 页面是否依赖服务端数据但静态生成时无法获取,若需动态数据,Next.js 13+可添加
export const dynamic = 'force-dynamic'标记为动态路由,旧版本改用getServerSideProps。 - 检查组件语法、未处理的Promise或缺失的依赖模块。
- 页面是否使用了客户端专属API(如
- 调整Netlify构建命令:将构建命令改为
CI=false npm run build,跳过严格模式下的构建检查。 - 本地复现问题:在本地执行
next build && next export,复现错误后直接在本地调试,减少部署测试成本。 - 核对环境变量:确认Netlify后台设置的环境变量与本地一致,缺失关键变量会导致静态生成失败。
- 检查插件兼容性:确保
@netlify/plugin-nextjs插件版本与你的Next.js版本匹配,建议升级至最新兼容版。
内容的提问来源于stack exchange,提问作者Dylan Baker
相关产品推荐
相关产品推荐

