May I ask why don't usegenerateStaticParams() about leerob.io

[tonywangcn]

@talpx0 That's my version of doing it. All the posts will be rendered during building time. Checkout my website https://tonywang.io if you're interested.

export const generateStaticParams = async () => {
  const allBlogs = getBlogPosts();  
  const paths = allBlogs.map((post)=> ({slug: post.slug}))
  return paths
}

[PieterDePauw]

First, "https://.../posts" would not be a valid URL. But the main server is indeed that the data is read from local sources. Each page load will also update the view counter

[talpx0]

First, "https://.../posts" would not be a valid URL. But the main server is indeed that the data is read from local sources. Each page load will also update the view counter

https://nextjs.org/docs/app/api-reference/functions/generate-static-params

• So ,my question is like,The generateStaticParams function can be used in combination with dynamic route segments to statically generate routes at build time instead of on-demand at request time. But since it is read from local resources,it will automatically get injected at build time?

[devjiwonchoi]

@talpx0 You're right, you can retrieve the slug and set it with generateStaticParams, which will generate the routes at the build time which I'd recommend.

leerob.io/app/blog/[slug]/page.tsx

Lines 10 to 13 in e9357c5

	export async function generateMetadata({
	params,
	}): Promise<Metadata | undefined> {
	let post = getBlogPosts().find((post) => post.slug === params.slug);

@PieterDePauw The URL can be valid in many ways for example using the route.ts, GitHub API, etc.