You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
9:45:30 PM: make: *** [Makefile:25: get-link-checker] Error 2
9:45:30 PM:
9:45:30 PM: "build.command" failed
9:45:30 PM: ────────────────────────────────────────────────────────────────
9:45:30 PM:
9:45:30 PM: Error message
9:45:30 PM: Command failed with exit code 2: npm run build:preview (https://ntl.fyi/exit-code-2)
9:45:30 PM:
9:45:30 PM: Error location
9:45:30 PM: In build.command from netlify.toml:
9:45:30 PM: npm run build:preview
9:45:30 PM:
9:45:30 PM: Resolved config
9:45:30 PM: build:
9:45:30 PM: command: npm run build:preview
9:45:30 PM: commandOrigin: config
9:45:30 PM: environment:
9:45:30 PM: - REVIEW_ID
9:45:30 PM: publish: /opt/build/repo/public
9:45:30 PM: publishOrigin: config
9:45:31 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
9:45:31 PM: Failing build: Failed to build site
However when I run npm install followed by npm run build:preview the process completes sucessfully.
@nate-double-u - Any ideas what might be going on here? If you can shed any light on what might be going wrong I'm happy to work on whatever fix is required 🙏🏻
The text was updated successfully, but these errors were encountered:
It looks like the link checker is failing. As a workaround to get things going again we could disable it, but we should do an investigation as to why it's stopped (Especially since it seems to be working locally).
Recently our netlify deploy previews have been failing to build, example https://app.netlify.com/sites/etcd/deploys/647c5d107e85bc000792009c
Logs state:
However when I run
npm install
followed bynpm run build:preview
the process completes sucessfully.@nate-double-u - Any ideas what might be going on here? If you can shed any light on what might be going wrong I'm happy to work on whatever fix is required 🙏🏻
The text was updated successfully, but these errors were encountered: