<Link> Element to Static Route Hits Route Loader Dynamically Anyway

[mattymattdev]

Which project does this relate to?

Router

Describe the bug

When you set up a static route with Nitro any Tanstack components to the static route will still attempt to call the loader dynamically.

If you are doing anything in the static route that is only available during the build phase, this will result in an error.

Hitting the link directly in the browser, through an Anchor () ref, or refreshing the page once you've errored out via your will load the page correctly via the Nitro-generated static site.

Treading lightly here as I know Static with Nitro implementation is still a WIP. 😄

Your Example Website or App

mattymattdev/symmetrical-octo-couscous@b3da210

Steps to Reproduce the Bug or Issue

1. Create a static route as per the docs
2. Do something in that route that requires something only available as a resource during build time
3. Link to the static route with a Link component
4. Build everything and navigate to your site
5. Click the and watch whatever you're trying to access on the client side fail even though it was supposed to be a static route

Expected behavior

As a user I expected my to work.

Screenshots or Videos

No response

Platform

• Ubuntu, building for Cloudflare Pages

Additional context

Rationale for bringing this up is that different pages and teams might become static at different times during the optimization lifecycles of a new web app and it would be nice if hunting potentially dynamically generated s wasn't necessary if you wanted to do that.

[schiller-manuel]

FYI: this prerender hook will not be available once we move off vinxi as we also won't have nitro available other then for deployment. however there will be a new way of prerendering.

That being said, can you please strip down the example to the bare minimum to not use a database etc.
Cannot run this as is.

[mattymattdev]

Thanks for taking a look @schiller-manuel.

That being said, can you please strip down the example to the bare minimum to not use a database etc.

I'll need to have a think about how best to replace my local db call with "something I didn't expect happen at runtime but only expected to happen at build time." Thoughts welcome.

[schiller-manuel]

just mock out the DB with some function calls that also log something ?

[mattymattdev]

just mock out the DB with some function calls that also log something ?

Ah, if that's all -- done! Just added a console log that one wouldn't expect to happen at runtime in prod for function called by a statically rendered route.

Thank you for your patience!

[schiller-manuel]

so is this working when hitting the URL directly by e.g. a hard refresh?

[mattymattdev]

so is this working when hitting the URL directly by e.g. a hard refresh?

Correct -- in production the prerender content is being served as expected when accessed by page refresh, a hard-coded <a ref= ... > (as in "not a <Link>"), or when the browser is navigated directly to the page.

I believe the behavior may be different in the development environment.

[schiller-manuel]

a client side navigation cannot use prerendered html. if you want to e.g. avoid the database being hit you would need to use a static server function to cache that.