@yao-pkg/pkg 6.3.1 → 6.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +6 -0
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -408,6 +408,12 @@ PKG_NODE_PATH=/path/to/node pkg app.js
408
408
 
409
409
  ## Troubleshooting
410
410
 
411
+ ### Error: Error [ERR_REQUIRE_ESM]: require() of ES Module
412
+
413
+ 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.
414
+
415
+ In most cases adding `--options experimental-require-module` to `pkg` command line will solve the issue.
416
+
411
417
  ### Error: Cannot find module XXX (when using `child_process`)
412
418
 
413
419
  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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yao-pkg/pkg",
3
- "version": "6.3.1",
3
+ "version": "6.3.2",
4
4
  "description": "Package your Node.js project into an executable",
5
5
  "main": "lib-es5/index.js",
6
6
  "license": "MIT",
@@ -32,7 +32,7 @@
32
32
  "picocolors": "^1.1.0",
33
33
  "picomatch": "^4.0.2",
34
34
  "prebuild-install": "^7.1.1",
35
- "resolve": "^1.22.0",
35
+ "resolve": "^1.22.10",
36
36
  "stream-meter": "^1.0.4",
37
37
  "tar": "^7.4.3",
38
38
  "tinyglobby": "^0.2.11",