TypeError when attempting SSG for /popular route with react-server build

[jinwatanabe]

Hi, I'm encountering an error while trying to implement Static Site Generation (SSG) for my /popular route using react-server.

Set up SSG configuration for /popular route
Run react-server build command

Error Message

Copyreact-server/0.0.0-experimental-9ed2d6f-20250125-9716750b building static for production
TypeError: paths.map is not a function
    at file:///home/jinwatanabe/workspace/tech-article/node_modules/@lazarv/react-server/lib/build/static.mjs:115:10
    at async file:///home/jinwatanabe/workspace/tech-article/node_modules/@lazarv/react-server/server/runtime.mjs:29:9

GitHub Repo

https://github.com/jinwatanabe/tech-article-app

Questions

Are there any known issues with SSG in the current experimental version?

Any guidance would be greatly appreciated!

[lazarv]

Hi @jinwatanabe,

the error is about the static paths defined by your export configuration function at https://github.com/jinwatanabe/tech-article-app/blob/main/react-server.config.mjs.

You are wrapping the paths into an object with a routes key, but you should just return an array of static routes as objects with at least a path property. You also don't need to use the remote flag on the route as that's only used for micro-frontend routes when consuming the route in another application by using RemoteComponent and you want to render the remote payload into a static file.

export default {
  root: "src/app",
  export() {
-    return {
+    return [
-      routes: [
        {
          path: "/popular",
-          remote: true,
        },
-      ],
+      ];
    };
  },

See more at https://react-server.dev/router/static

[jinwatanabe]

Thank you!!　@lazarv

React-server is the best framework to replace Next.js. I look forward to its further development. I also plan to publish tutorials to make it more popular in Japan.

[lazarv]

Thanks, @jinwatanabe! I really appreciate it, and I’m looking forward to reading your tutorials. Always great to see different perspectives and approaches!

As for @lazarv/react-server, it's definitely not in a position to replace Next.js, and honestly, that’s not the goal. I see it more as an alternative for React developers who need something lightweight for small, quick projects. That said, there's still a long road ahead before I can call it production-ready. A lot of key features are still missing (proper Edge support being a big one) and there's plenty of room for optimization.