fix: Windows-rendering of content (#5476)

Co-authored-by: Claudio Wunder <[email protected]>

Author: bmuenzenmeyer

next.dynamic.mjs

@@ -1,6 +1,6 @@
 'use strict';
 
-import { join } from 'node:path';
+import { join, normalize, sep } from 'node:path';
 import { readFileSync } from 'node:fs';
 import { VFile } from 'vfile';
 import remarkGfm from 'remark-gfm';
@@ -41,13 +41,18 @@ const getAllPaths = async () => {
     (locale = '') =>
     (files = []) =>
       sourcePages.map(filename => {
-        const path = filename.replace(nextConstants.MD_EXTENSION_REGEX, '');
+        // remove the index.md(x) suffix from a pathname
+        let pathname = filename.replace(nextConstants.MD_EXTENSION_REGEX, '');
+        // remove trailing slash for correct Windows pathing of the index files
+        if (pathname.length > 1 && pathname.endsWith(sep)) {
+          pathname = pathname.substring(0, pathname.length - 1);
+        }
 
         return {
-          pathname: path,
+          pathname: normalize(pathname),
           filename: filename,
           localised: files.includes(filename),
-          routeWithLocale: `${locale}/${path}`,
+          routeWithLocale: `${locale}/${pathname}`,
         };
       });
 
@@ -99,7 +104,7 @@ export const getMarkdownFile = (
   // which prevents any malicious attempts to access non-allowed pages
   // or other files that do not belong to the `sourcePages`
   if (routes && routes.length) {
-    const route = routes.find(route => route.pathname === pathname);
+    const route = routes.find(route => route.pathname === normalize(pathname));
 
     if (route && route.filename) {
       // this determines if we should be using the fallback rendering to the default locale