init

project-wl-kuaidiyuan-uniapp-vue3/node_modules/_esbuild-windows-64@0.14.53@esbuild-windows-64/README.md

@@ -0,0 +1,3 @@
+# esbuild
+
+This is the Windows 64-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.

project-wl-kuaidiyuan-uniapp-vue3/node_modules/_esbuild-windows-64@0.14.53@esbuild-windows-64/bin/esbuild

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+
+// Unfortunately even though npm shims "bin" commands on Windows with auto-
+// generated forwarding scripts, it doesn't strip the ".exe" from the file name
+// first. So it's possible to publish executables via npm on all platforms
+// except Windows. I consider this a npm bug.
+//
+// My workaround is to add this script as another layer of indirection. It'll
+// be slower because node has to boot up just to shell out to the actual exe,
+// but Windows is somewhat of a second-class platform to npm so it's the best
+// I can do I think.
+const esbuild_exe = require.resolve('esbuild-windows-64/esbuild.exe');
+const child_process = require('child_process');
+child_process.spawnSync(esbuild_exe, process.argv.slice(2), { stdio: 'inherit' });

project-wl-kuaidiyuan-uniapp-vue3/node_modules/_esbuild-windows-64@0.14.53@esbuild-windows-64/package.json

@@ -0,0 +1,20 @@
+{
+  "name": "esbuild-windows-64",
+  "version": "0.14.53",
+  "description": "The Windows 64-bit binary for esbuild, a JavaScript bundler.",
+  "repository": "https://github.com/evanw/esbuild",
+  "license": "MIT",
+  "preferUnplugged": false,
+  "engines": {
+    "node": ">=12"
+  },
+  "os": [
+    "win32"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "__npminstall_done": true,
+  "_from": "esbuild-windows-64@0.14.53",
+  "_resolved": "https://registry.npmmirror.com/esbuild-windows-64/-/esbuild-windows-64-0.14.53.tgz"
+}

project-wl-kuaidiyuan-uniapp-vue3/node_modules/esbuild-windows-64/README.md

@@ -0,0 +1,3 @@
+# esbuild
+
+This is the Windows 64-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.

project-wl-kuaidiyuan-uniapp-vue3/node_modules/esbuild-windows-64/bin/esbuild

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+
+// Unfortunately even though npm shims "bin" commands on Windows with auto-
+// generated forwarding scripts, it doesn't strip the ".exe" from the file name
+// first. So it's possible to publish executables via npm on all platforms
+// except Windows. I consider this a npm bug.
+//
+// My workaround is to add this script as another layer of indirection. It'll
+// be slower because node has to boot up just to shell out to the actual exe,
+// but Windows is somewhat of a second-class platform to npm so it's the best
+// I can do I think.
+const esbuild_exe = require.resolve('esbuild-windows-64/esbuild.exe');
+const child_process = require('child_process');
+child_process.spawnSync(esbuild_exe, process.argv.slice(2), { stdio: 'inherit' });

project-wl-kuaidiyuan-uniapp-vue3/node_modules/esbuild-windows-64/package.json

@@ -0,0 +1,20 @@
+{
+  "name": "esbuild-windows-64",
+  "version": "0.14.53",
+  "description": "The Windows 64-bit binary for esbuild, a JavaScript bundler.",
+  "repository": "https://github.com/evanw/esbuild",
+  "license": "MIT",
+  "preferUnplugged": false,
+  "engines": {
+    "node": ">=12"
+  },
+  "os": [
+    "win32"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "__npminstall_done": true,
+  "_from": "esbuild-windows-64@0.14.53",
+  "_resolved": "https://registry.npmmirror.com/esbuild-windows-64/-/esbuild-windows-64-0.14.53.tgz"
+}