[windows] Add Windows compatibility for the resolve ESBuild plugin

Previously, the separator for the filter regex was hardcoded to `/` (Unix separator).
Now, instead of hardcoding the separator, we are using the cross-platform `path.join` function. It's result is regex escaped using the `escape-string-regexp` library.

Signed-off-by: Costin Sin <[email protected]>

Author: costinsin

packages/open-next/package.json

@@ -46,7 +46,8 @@
     "chalk": "^5.3.0",
     "esbuild": "0.19.2",
     "path-to-regexp": "^6.2.1",
-    "promise.series": "^0.2.0"
+    "promise.series": "^0.2.0",
+    "escape-string-regexp": "^5.0.0"
   },
   "devDependencies": {
     "@types/aws-lambda": "^8.10.109",

packages/open-next/src/plugins/resolve.ts

@@ -10,6 +10,8 @@ import type {
 } from "types/open-next";
 
 import logger from "../logger.js";
+import path from "path";
+import escapeStringRegexp from 'escape-string-regexp';
 
 export interface IPluginSettings {
   overrides?: {
@@ -44,7 +46,10 @@ export function openNextResolvePlugin({
     name: "opennext-resolve",
     setup(build) {
       logger.debug(`OpenNext Resolve plugin for ${fnName}`);
-      build.onLoad({ filter: /core\/resolve.js/g }, async (args) => {
+      const filter = new RegExp(
+        escapeStringRegexp(path.join("core", "resolve.js"), "g"),
+      );
+      build.onLoad({ filter }, async (args) => {
         let contents = readFileSync(args.path, "utf-8");
         //TODO: refactor this. Every override should be at the same place so we can generate this dynamically
         if (overrides?.wrapper) {