This repository has been archived by the owner on Jan 13, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
Executable broken when called with PKG_EXECPATH
set to its own absolute path
#1565
Comments
ExplanationLines 77 to 89 in 2ef4cd9
|
Module._load(ENTRYPOINT, null, true); |
Value of ENTRYPOINT
(either undefined
or a non–existent path) is used to call the _load
function, producing an error.
Footnotes
-
Namely,
'/path/to/current/directory/argument'
↩
It turns out that there aren't other solutions apart from unsetting |
This was referenced Mar 24, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of pkg are you using?
5.5.2
What version of Node.js are you using?
16.14.0
What operating system are you using?
Ubuntu 20.04
What CPU architecture are you using?
x86_64
What Node versions, OSs and CPU architectures are you building for?
node16-linux-x64
Describe the Bug
Calling an executable created with
pkg
with thePKG_EXECPATH
environment variable set to the absolute path of the executable produces an error.Expected Behavior
Setting the
PKG_EXECPATH
environment variable to the absolute path of the executable should not produce any error:To Reproduce
Setting the
PKG_EXECPATH
environment variable to the absolute path of the executable produces an error:The text was updated successfully, but these errors were encountered: