Misleading missing getStaticPaths error with configured redirects and dynamic routes

[ChrisRenfrow]

Astro Info

Astro                    v4.15.8
Node                     v18.20.3
System                   Linux (x64)
Package Manager          unknown
Output                   static
Adapter                  none
Integrations             none

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

If I have a route like this:

/categories/[category]/
+-- index.astro
+-- [page].astro

In which each endpoint exports getStaticPaths, one for matching the base route with the category param, another for the category param with pagination.

If I include the following in astro.config.mjs:

// ...
redirects: {
  '/categories/[category]': '/category/[category]/1',
},
// ...

Running astro build yields this error:

[ERROR] [build] Failed to call getStaticPaths for /categories/[category]
[GetStaticPathsRequired] `getStaticPaths()` function is required for dynamic routes. Make sure that you `export` a `getStaticPaths` function from your dynamic route.

What's the expected result?

I would expect this setup to build without errors. It's my understanding that configured redirects are supported in static render mode, and even if this isn't the case, the error doesn't make sense and took far too long to for me to track down the source of the problem.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/withastro-astro-vyvufy?file=src%2Fpages%2Findex.astro

Participation

• I am willing to submit a pull request for this issue.

[robclancy]

I had to downgrade all the way to 5.9.2 because of this. Whatever the issue was it's back.

[ematipico]

After some investigation, I conclude that this issue is not a bug.

As we document, dynamic redirects are possible only if both left (origin) and right (destination) have the same number of dynamic parameters. In this particular case, origin and destination have different parameters:

• The origin part has one dynamic parameter, which is [category]
• The destination part has two dynamic parameters, which are [category] and [page]

You can't have a destination that combines dynamic and static parameters, such as /[category]/1. This isn't permitted and is not documented.

The only workaround is to define static redirects, for example:

defineConfig({
  "/category-name/": "/category-name/1"
})

Where category-name is the resolved [category] dynamic parameter.

[robclancy]

How is something that worked and then broke because of a change not a bug? What a joke. And what a terrible restriction for no reason.