@yao-pkg/pkg 6.3.0 → 6.3.2

package/README.md

@@ -408,6 +408,12 @@ PKG_NODE_PATH=/path/to/node pkg app.js
 
 ## Troubleshooting
 
+### Error: Error [ERR_REQUIRE_ESM]: require() of ES Module
+
+This error is tracked by issue [#16](https://github.com/yao-pkg/pkg/issues/16#issuecomment-1945486658). Follow the link in oder to find a workaround.
+
+In most cases adding `--options experimental-require-module` to `pkg` command line will solve the issue.
+
 ### Error: Cannot find module XXX (when using `child_process`)
 
 When using `child_process` methods to run a new process pkg by default will invoke it using NodeJS runtime that is built into the executable. This means that if you are trying to spawn the packaged app itself you will get above error. In order to avoid this you must set `PKG_EXECPATH` env set to `""`:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yao-pkg/pkg",
-  "version": "6.3.0",
+  "version": "6.3.2",
   "description": "Package your Node.js project into an executable",
   "main": "lib-es5/index.js",
   "license": "MIT",
@@ -32,10 +32,10 @@
     "picocolors": "^1.1.0",
     "picomatch": "^4.0.2",
     "prebuild-install": "^7.1.1",
-    "resolve": "^1.22.0",
+    "resolve": "^1.22.10",
     "stream-meter": "^1.0.4",
     "tar": "^7.4.3",
-    "tinyglobby": "^0.2.9",
+    "tinyglobby": "^0.2.11",
     "unzipper": "^0.12.3"
   },
   "devDependencies": {

package/prelude/bootstrap.js

@@ -1725,7 +1725,7 @@ function payloadFileSync(pointer) {
     fs.promises.read = util.promisify(fs.read);
     fs.promises.realpath = util.promisify(fs.realpath);
     fs.promises.fstat = util.promisify(fs.fstat);
-    fs.promises.statfs = util.promisify(fs.fstat);
+    fs.promises.statfs = util.promisify(fs.statfs);
     fs.promises.access = util.promisify(fs.access);
 
     // TODO: all promises methods that try to edit files in snapshot should throw