fix: better support of .node files

[robertsLando]

When a .node file is required pkg copies it in a temporary folder like /tmp/<hash>/addon.node the problem is that for modules like sharp this isn't working as them are statically linked to other .so files using relative paths. This pr will copy the entire module folder inside the temporary directory, this allows also to remove the tryImport function as there is no reason to try again if that fails.

I tested this on my end and it's working

I also grouped all hash folders inside pkg folder to be sure that the copy will run when users will update pkg, otherwise the copy may not be done when the folder already exists but was created with a previous pkg version

cc @jesec @leerob @erossignon

Fixes #1075

[robertsLando]

@leerob Could you take a look into this please? If it looks ok to you could you also make a patch release? I need this in a project I'm working on, thannks :)

[leerob]

Thanks for the review, @jesec! 🙏

[robertsLando]

@leerob new patch when possible please 🙏🏼

[ghost]

Thank u for this patch. But now i have the following error.

Something went wrong installing the "sharp" module

Cannot read property '1' of null

Possible solutions:
- Install with the --verbose flag and look for errors: "npm install --ignore-scripts=false --verbose sharp"
- Install for the current runtime: "npm install --platform=win32 --arch=x64 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install

Could you plase help me?

[robertsLando]

Fixed on master

[plckr]

@Grewamor I'm having the same problem, and since I'm using yarn I don't know how can I install it to specific platform and arch, AFAIK yarn makes it impossible to choose

[chuongmep]

Any update for now ? I'm facing with same issue

[benjaminhera]

Any updates on this?