fix: Avoid ESBuild destroying Proxy in __toESM

[Danielku15]

Fixes #153

When transpiling typescript (or ESM) toa ESBuild, it translates imports in a way like this:

TypeScript:

import path, { join } from 'node:path';

JS:

"use strict";
var __create = Object.create;
var __defProp = Object.defineProperty;
var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
var __getOwnPropNames = Object.getOwnPropertyNames;
var __getProtoOf = Object.getPrototypeOf;
var __hasOwnProp = Object.prototype.hasOwnProperty;
var __name = (target, value) => __defProp(target, "name", { value, configurable: true });
var __copyProps = (to, from, except, desc) => {
  if (from && typeof from === "object" || typeof from === "function") {
    for (let key of __getOwnPropNames(from))
      if (!__hasOwnProp.call(to, key) && key !== except)
        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
  }
  return to;
};
var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__getProtoOf(mod)) : {}, __copyProps(
  // If the importer is in node compatibility mode or this is not an ESM
  // file that has been converted to a CommonJS file using a Babel-
  // compatible transform (i.e. "__esModule" has not been set), then set
  // "default" to the CommonJS "module.exports" for node compatibility.
  isNodeMode || !mod || !mod.__esModule ? __defProp(target, "default", { value: mod, enumerable: true }) : target,
  mod
));
var import_node_path = __toESM(require("node:path"));
import_node_path.default.join("", "");
(0, import_node_path.join)("", "");

As we can see, it created a complete new object using Object.create copying all individual properties over. This way it translates ESM modules to CJS during runtime respecting the __esModule flags. This completely destroys our Proxy object representing our fake imported module.

With this fix we ensure Object.create also will create again a Proxy object restoring our runtime dynamic module.