You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just discovered after some digging that, for a module to work with node-bindings in a project that uses webpack, that module needs to be included in externals in webpack.config.js so that its code ends up in a directory from which its package.json can be found. Would it make sense to include this in the readme?
The text was updated successfully, but these errors were encountered:
If someone else struggles with this, here's what worked for me. I am using the npm package objc which depends on ref and ffi, who in turn depend on bindings.
Adding bindings as an external, as suggested in most threads, did not work. Neither did objc. But this did the trick in webpack.config.js:
I just discovered after some digging that, for a module to work with
node-bindings
in a project that useswebpack
, that module needs to be included inexternals
inwebpack.config.js
so that its code ends up in a directory from which itspackage.json
can be found. Would it make sense to include this in the readme?The text was updated successfully, but these errors were encountered: