roll back changes to next-data/providers/blogData.ts

Author: dario-piotrowicz

apps/site/CLOUDFLARE.md

@@ -75,7 +75,7 @@ The following is an incomplete list of tasks and problems that still need to be
 - [x] reimplement `getMarkdownFiles` in `next.helpers.mjs` to be generated at build time
   - this can be accomplished either via a npm/turbo prebuild task, or possibly as part of next.js SSG/staticProps but
   - [ ] we need to ensure that we don't end up accidentally downloading this big file to the client as part of hydration
-  - [ ] once we have easy access to the list of files, we should roll back changes to `next-data/providers/blogData.ts`
+  - [x] once we have easy access to the list of files, we should roll back changes to `next-data/providers/blogData.ts`
 - [ ] back out most changes from `next.dynamic.mjs`
   - [ ] instead of using runtime detection via `globalThis.navigator?.userAgent`, we should instead use `alias` feature in `wrangler.toml` to override the implementation of `node:fs` calls but only when running in workerd as we need the build to keep on running in node.js for SSG to work
   - [ ] could we reimplement the `existsAsync` call as sync `exists` which consults `getMarkdownFiles` from the task above? alternatively

apps/site/next-data/providers/blogData.ts

@@ -1,10 +1,10 @@
 import { cache } from 'react';
 
-// import generateBlogData from '@/next-data/generators/blogData.mjs';
+import generateBlogData from '@/next-data/generators/blogData.mjs';
 import { BLOG_POSTS_PER_PAGE } from '@/next.constants.mjs';
 import type { BlogPostsRSC } from '@/types';
 
-const { categories, posts } = { categories: [], posts: [] };
+const { categories, posts } = await generateBlogData();
 
 export const provideBlogCategories = cache(() => categories);