Asset relocator messes up some packages

[cesarvarela]

Preflight Checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

• Electron Forge Version:
• Electron Version:
  *v13.0.1
• Operating System:
  • Windows 10
• Last Known Working Electron Forge version::
  n/a

Expected Behavior

I'm working on a project using 2 native modules:
https://github.com/kristian/displays & https://github.com/octalmage/robotjs

The displays package works and the robotjs package doesn't.

Actual Behavior

The diaplays package gets copied to the native_modules folder and works without issue, the robotjs package gets copied too but an intermediate (?) module is created:

wich contains this:

And results in this error:

Replacing the weird intermediate module with the actual robotjs binary works, so I guess the static analysis is triggering a different code path for the robotjs module that is not actually needed and should behave the same as with the other module.

[ivancuric]

Does it work with https://github.com/timfish/forge-externals-plugin or when changing the asset relocator loader to this fork https://www.npmjs.com/package/@timfish/webpack-asset-relocator-loader ?

[cesarvarela]

Thanks, tried both and none worked, the externals plugin copied some modules to the node_modules folder but some are missing still it seems. The asset relocator one did exactly the same as the one from marshalofsound.