fix: use normalizePathSeparators in formatAppFilePath for Windows compatibility

[kushdab]

Summary

formatAppFilePath in app-route-graph.ts was using inline .replace(/\\\\/g, "/") to normalize path separators instead of the shared normalizePathSeparators utility already imported at the top of the file.

This fixes two call sites within formatAppFilePath:

- const relativePath = path.relative(appDir, filePath).replace(/\\\\/g, "/");
+ const relativePath = normalizePathSeparators(path.relative(appDir, filePath));
  const parsedPath = path.parse(relativePath);
- const withoutExtension = path.join(parsedPath.dir, parsedPath.name).replace(/\\\\/g, "/");
+ const withoutExtension = normalizePathSeparators(path.join(parsedPath.dir, parsedPath.name));

normalizePathSeparators was already imported and used in scanWithExtensions (file-matcher.ts) for the same reason — this migrates the remaining per-callsite inline replacements in app-route-graph.ts to the shared utility, consistent with how #1578 and #1604 addressed the same class of bug elsewhere.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@vinext/cloudflare@2426

npm i https://pkg.pr.new/vinext@2426

commit: ed8125a