bozon icon indicating copy to clipboard operation
bozon copied to clipboard

packaging application with native modules

Open ceonizm opened this issue 2 years ago • 1 comments

Hello,

I was wondering how do you deal with native modules. When doing webpack I see bozon create a package.json in the build folder from its manifest function: this package.json doesn't comport any dependencies ; I totally understand it and why, as webpack is supposed to pack all the code in one file, but I don't see how to deal with the case of native modules that can't be packed.

In my current task I want to build an app with node-hid so at the end I need to have it listed in the package.json in the build/{env} folder in order electron-builder can handle it.

Is there a mechanism or a config in bozon that allows us to do that (eg: specify a list of depedencies to add) or does this kind of task is doable in webpack with a plugin ?

ceonizm avatar Jul 27 '21 09:07 ceonizm

I finally succeeded to achieve my aim by writing a small webpack plugin that does the injection during the webpack phase. I feel it a clean way to do it at that time, but I tend to think that it would be a good thing if Bozon should supply that kind of plugin to avoid people to rewrite it.

here is a version of the plugin I wrote if it can help or inspire somebody :) https://github.com/ceonizm/BozonPackageDependencyInjectorPlugin

ceonizm avatar Jul 27 '21 13:07 ceonizm