Normalize file paths in deadLinkChecker and update documentation links for clarity

Author: Mohamed-Hashem

scripts/deadLinkChecker.js

@@ -80,7 +80,9 @@ async function buildAnchorMap(files) {
     const content = await readFileWithCache(filePath);
     const anchors = extractAnchorsFromContent(content);
     if (anchors.size > 0) {
-      anchorMap.set(filePath, anchors);
+      // Normalize path to use consistent separators
+      const normalizedPath = path.normalize(filePath);
+      anchorMap.set(normalizedPath, anchors);
     }
   }
 }
@@ -244,7 +246,9 @@ async function validateLink(link) {
       }
     }
 
-    const fileAnchors = anchorMap.get(targetFile);
+    // Normalize target file path for comparison with anchorMap keys
+    const normalizedTargetFile = path.normalize(targetFile);
+    const fileAnchors = anchorMap.get(normalizedTargetFile);
 
     if (!fileAnchors || !fileAnchors.has(anchorId)) {
       return {

src/content/blog/2024/10/21/react-compiler-beta-release.md

@@ -86,7 +86,7 @@ React Compiler can also be used to compile libraries. Because React Compiler nee
 
 Because your code is pre-compiled, users of your library will not need to have the compiler enabled in order to benefit from the automatic memoization applied to your library. If your library targets apps not yet on React 19, specify a minimum `target` and add `react-compiler-runtime` as a direct dependency. The runtime package will use the correct implementation of APIs depending on the application's version, and polyfill the missing APIs if necessary.
 
-[You can find more docs on this here.](/reference/react-compiler/target#using-the-compiler-on-libraries)
+[You can find more docs on this here.](/reference/react-compiler/target#targeting-react-17-or-18)
 
 ## Opening up React Compiler Working Group to everyone {/*opening-up-react-compiler-working-group-to-everyone*/}