Describe the problem

It's extremely tedious (especially when converting a Sapper app with lots of old, broken links) to

1. Run a build (with the static adapter)
2. See a single 404 error, which ends the build
3. Fix that single error
4. Repeat the above for all 37 404s.

Describe the proposed solution

It would be far better if the first encounter with a 404 didn't immediately bail on the rest of the adapter phase of the build. Sapper used to give a full list of all files, including links that 404'ed. It would be nice if SvelteKit either did the same, or at least produced a full list of 404s instead of showing you one error for each build attempt.

Alternatives considered

I mean, yeah. I can just run the build one time for every single error as described above, but that takes an order of magnitude more time/compute and attention. It's nuts.

The other alternative is to stay on Sapper.

Importance

would make my life easier

Additional Information

...failure number 23...

...fix the code for 5 seconds...
...run npm run build...
...81 seconds later...
...failure number 24...

...fix the code for 5 seconds...
...run npm run build...
...81 seconds later...
...failure number 25...

(you get the picture, and 81 seconds is accurate 😆)