should this be put into the docs?

Thanks for this! Also added NotFoundError to the list of allowed things to throw for the same reason.

After some thought on this, I'm closing this, since this is more around a user's eslint setup. If you are using typescript-eslint's recommended setup, you wouldn't get this error from eslint.

The way to suppress this error is either turn off the rule, or change it to a warning. Both of which is done in the end user's eslint config.

We could document this in the Router docs, but this does not seem feasible considering that people could have other various rules in their configs that could also cause issues in their dev workflow.

A user customizing the eslint config's from upstream providers (like typescript-eslint, airbnb, antfu) to suite their project's requirements is quite common. This would fall into that category.