-
Notifications
You must be signed in to change notification settings - Fork 1k
Not working with sharp again "Cannot include directory %1 into executable." #1918
Comments
Try to use |
Also facing this issue. Adding "node_modules/sharp/**" to asset seems to work when compiling for the linux platform. This is the platform where my development happens. However, it does not help with cross compiling for win platform. Below is what I get when I try to run exe on Windows platform.
Checking the AppData folder shows that the files ARE in that folder.
|
did you try reinstalling sharp for windows before you compiled your pkg binary? E.g. Sharp uses native .node files that are compiled and platform specific, so you are trying to run a linux compiled native node module on a windows machine. Do you have the ability to build your windows pkg distributable on windows itself natively? |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit. |
What version of pkg are you using?
5.7.0
What version of Node.js are you using?
16.15.0
What operating system are you using?
linux
What CPU architecture are you using?
amd64
What Node versions, OSs and CPU architectures are you building for?
node16-linux-64
Describe the Bug
When I run pkg there are warnings
To Reproduce
Try running pkg with sharp as a dependency. You can add these to package.json which I thought would fix it but it didn't.
According to #1075 sharp should be working but it's not.
#229 is a similar issue but like many issues in this vercel pkg repository it got closed automatically even though it's still not working.
The text was updated successfully, but these errors were encountered: