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
During our development process using a CMS it's been common to encounter errors as the CMS is being shored up. Code doesn't properly handle missing data etc.
Instead of building the thousands of pages and listing the 10-20 that are failing, is there a way to just stop the static site build immediately on any error?
This would save considerable CI build time.
Just an example of an unhandled error it would be nice to fail immediately on.
1:58:51 PM: Unhandled error during request: Error: DestinationType is Content reference, but no content reference is selected1:58:51 PM: at Object.default (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:58990:23)1:58:51 PM: at traverse (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:52390:44)1:58:51 PM: at /opt/build/repo/.next/serverless/pages/conditions/[slug].js:37820:381:58:51 PM: at /opt/build/repo/.next/serverless/pages/conditions/[slug].js:29318:151:58:51 PM: at baseForOwn (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:27383:24)1:58:51 PM: at Function.mapValues (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:37819:7)1:58:51 PM: at traverse (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:52408:45)1:58:51 PM: at /opt/build/repo/.next/serverless/pages/conditions/[slug].js:52420:161:58:51 PM: at /opt/build/repo/.next/serverless/pages/conditions/[slug].js:60044:501:58:51 PM: at step (/opt/build/repo/.next/serverless/pages/conditions/[slug].js:59999:23)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
During our development process using a CMS it's been common to encounter errors as the CMS is being shored up. Code doesn't properly handle missing data etc.
Instead of building the thousands of pages and listing the 10-20 that are failing, is there a way to just stop the static site build immediately on any error?
This would save considerable CI build time.
Just an example of an unhandled error it would be nice to fail immediately on.
Beta Was this translation helpful? Give feedback.
All reactions