-
Notifications
You must be signed in to change notification settings - Fork 772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using node-fs-extra with pkg (create executables) is causing an error in universalify #901
Comments
It seems |
Target for compiling is windows x86 |
fixed in pkg, thanks for pointing out the problem |
FYI to others, there's a similar issue when using DataDog Trace. |
@Infern1, I'm seeing the same error with |
Anecdotally, it seems that I am able to use the latest version of |
So patch is merged in pkg, no clue when they plan to release a new version. At least with the fix in place it is working. Using npm from git |
@Infern1 It seams to be release in version 5.2.0 of pkg : https:/vercel/pkg/releases/tag/5.2.0 I still doesn't understand the link with fs-extra, there is not pkg dependency I think ? For now I'll rollback to v 9.1.0 |
In my case it's the lib Thank you for the lead. |
This reverts commit 34ae6f2. See jprichardson/node-fs-extra#901
Same for [email protected], I have to downgrade fs-extra to 9.1.0 or I will have the same issue for compiled binary which target is linux. |
This reverts commit 34ae6f271a732fab407c42f6259ea4c5baa424d7. See jprichardson/node-fs-extra#901
fs-extra
version:I'm using pkg for creating binaries of my NodeJS program. When running directly via NodeJS everything is working as should. However when I created my executable now with fs-extra it stops:
I tried to look in
index.js
from universalify however at least for me it doesn't make sense.The text was updated successfully, but these errors were encountered: