Fixes #5442.

/cc @tony-sull & @bholmesdev

Changes

#3087 changed the type of Params from Record<string, string | undefined> to Record<string, string | number | undefined> to formerly allow getStaticPaths to return numbers.

However, as the change was made to Params and not GetStaticPathsResult or GetStaticPathsItem, it also affects Astro.params.

This PR essentially moves the change made in #3087 from Params to GetStaticPathsItem, reverting the type of Astro.params while keeping the type of getStaticPaths.

Note that while looking into this, I found this comment by @bholmesdev:

• if you pass a number to params.year in your getStaticPaths, it should still be a number when destructuring Astro.params. If not, that's a bug.
• if you created an SSR dynamic route like [year].astro, year will always be a string (even if it could be parsed to a number). This is where string -> number conversion would be manual.

In my experience, Astro.params never contains numbers, not even in static mode. While reviewing, please consider that this PR changes the types to match the behaviour, although judging by this comment, we might want to change the behaviour to match the types instead.

Testing

This is testable like so:

const artist: string | undefined = Astro.params.artist;

I haven't found any type definition tests to which this one could be added.

Docs

From what I understand, this change is in line with the current docs:

params are encoded into the URL, so only strings are supported as values.