docs(start/framework/routing): add 404 route instructions

[davidbielik]

clarifies 404 route based on #13701 (reply in thread)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4ca35e5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[timdorr]

@Hardanish-Singh Please stop with these approvals. They are just noise.

[timdorr]

Thanks!

Please submit another PR so we can get something added to the file routing guide as well.

[ashbreeze]

@davidbielik One downside to this method is that the 404 page will then return a 200 status code. This can be alleviated by adding a loader to the 404 page that always fails, eg:

export function loader() {
  return data(null, 404);
}

Not sure if this is a good pattern, but it seems to work reliably.

[davidbielik]

@davidbielik One downside to this method is that the 404 page will then return a 200 status code. This can be alleviated by adding a loader to the 404 page that always fails, eg:

export function loader() {
  return data(null, 404);
}

Not sure if this is a good pattern, but it seems to work reliably.

Hey, yes I cover that in the follow-up PR: #13771