feat: improve found routes logging and bump x2

Author: brrock

README.md

@@ -61,7 +61,7 @@ module.exports = nextConfig;
 > This tool generates a standalone bundle with no backend. 
 > - **Server Logic:** Features like Server Actions, `cookies()`, and Middleware are not supported.
 > - **Dynamic Routes:** You must use `generateStaticParams` for any dynamic paths (e.g., `[id].tsx`) to ensure they are pre-rendered into the `out/` directory before bundling.
-> - **RSC:** React Server Components are supported only insofar as they can be statically rendered to HTML at build time.
+> - **RSC:** React Server Components are supported if they can be statically rendered to HTML at build time.
 
 ### 2. Build Your Next.js App
 

index.ts

@@ -33,7 +33,10 @@ const { inputDir, outputFile } = parseArgs();
 console.log(`📖 Parsing Next.js output from: ${inputDir}`);
 const parsed = await parseNextOutput(inputDir);
 
-console.log(`📦 Found ${parsed.routes.length} routes:`, parsed.routes.map((r: { path: string }) => r.path));
+console.log(`📦 Found ${parsed.routes.length} routes:`);
+for (const route of parsed.routes) {
+  console.log(`   ${route.path}`);
+}
 
 console.log(`🔧 Inlining assets...`);
 const inlined = await inlineAssets(parsed);

package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-single-file",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Convert Next.js static export to a single HTML file with hash routing",
   "bin": {
     "next-single-file": "dist/cli.js"