Module could not be found | libnut.node

[jonkad]

Hi ✌️ ,

I'm also currently switching from robotJS to nut.js and it seems I've got an equal issue, but with electron-builder...
Maybe this has also happened to someone who have a solution?

Thanks a lot 😄

On unpacked asar the message mentioned C:\Program Files\ Control\resources\app\node_modules@nut-tree\libnut-win32\build\Release\libnut.node

"dependencies": {
        "@nut-tree/nut-js": "^2.0.2-next.20220121214305",
        "electron-updater": "^4.6.1",
    },
    "devDependencies": {
        "electron": "^15.3.5",
        "electron-builder": "^22.14.5",
        "electron-notarize": "^1.1.1",
        "electron-rebuild": "^3.2.7",
        "electron-updater": "^4.6.1"
    }

[s1hofmann]

Hi @jonkad 👋

Is this error happening on your dev machine, or after shipping it to another box?

[jonkad]

Hi @s1hofmann,

This happened after shipping. On dev mashine and some others everything is fine.

[s1hofmann]

Did you make sure to meet the Windows requirements on the target machine?

[jonkad]

Ah, is that necessary on the target machines as well?
On the DEV / Build machine it is of course installed.

[s1hofmann]

is that necessary on the target machines as well?

Yes, these are runtime requirements. I'll highlight this more clearly in the docs 👍

[jonkad]

Thank you for your assistance! And forgive me for the carelessness 😉

[s1hofmann]

You're welcome. Would be nice to hear how you learned about nut.js, considering your move from robot.js?

[augustnmonteiro]

@s1hofmann is there a way to ship the runtime requirements together with the installer?

[GaurangTandon]

Hi @s1hofmann 👋

Often, the users of automation apps (think support desk agents) are not admin users. So, if an app built using libraries like nut.js is shipped to them, they will not have the permission to install VCRedist (Windows requirement) on their system.

This is also noted by the MS official docs (link) and their suggestion in such case is to do "local deployment": copy the relevant .dll files in the same folder as the .node/.exe files.

I tried the same technique with libnut.node, unfortunately, it did not work. I want to confirm from you if you are aware of any specifics in libnut.node that may cause local deployment to not work?

Local deployment is crucial for such types of applications (non-admin users), and also for building portable binaries of apps. So, it would be great if it worked.

[s1hofmann]

nut-tree/libnut-core#130

[GaurangTandon]

Thanks @s1hofmann , I just tried this again and it works! (imported libnut snapshot and did libnut.keyTap/typeString, on a PC without VCredist installed)

[GaurangTandon]

You may wish to update the docs for first steps on Windows once a new nut.js release is out.