fix: Handle [extname] in normalizePath function (#137)

Deal with [extname] being used in user defined filename definitions in their bundler configs.

Author: nsdeschenes

.changeset/thirty-cheetahs-teach.md

@@ -0,0 +1,10 @@
+---
+"@codecov/bundler-plugin-core": patch
+"@codecov/nuxt-plugin": patch
+"@codecov/rollup-plugin": patch
+"@codecov/sveltekit-plugin": patch
+"@codecov/vite-plugin": patch
+"@codecov/webpack-plugin": patch
+---
+
+Update normalizePath function to handle [hash][extname] case.

packages/bundler-plugin-core/src/utils/__tests__/normalizePath.test.ts

@@ -67,6 +67,22 @@ const tests: Test[] = [
     },
     expected: "test.*.chunk.js",
   },
+  {
+    name: "handle case where [extname] is used",
+    input: {
+      path: "test.12345678.js",
+      format: "[name].[hash][extname]",
+    },
+    expected: "test.*.js",
+  },
+  {
+    name: "input path with no extension present",
+    input: {
+      path: "test.12345678",
+      format: "[name].[hash]",
+    },
+    expected: "test.*",
+  },
 ];
 
 describe("normalizePath", () => {

packages/bundler-plugin-core/src/utils/normalizePath.ts

@@ -34,8 +34,16 @@ export const normalizePath = (path: string, format: string): string => {
     )})`;
 
     // grab the ending delimiter and create a regex group for it
-    const endingDelimiter =
+    let endingDelimiter =
       format.at(match.hashIndex + match.hashString.length) ?? "";
+
+    // If the ending delimiter is `[extname]` there won't be a
+    // `.<file-extension>` so we need to replace it with a `.` for the
+    // handling the actual filename, which will have the `.` in the * string.
+
+    if (endingDelimiter === "[") {
+      endingDelimiter = ".";
+    }
     const endingRegex = `(?<endingDelimiter>${escapeRegex(endingDelimiter)})`;
 
     // create a regex that will match the hash