How to bundle external JS scripts with an extension?

Swader

My extension relies on a server-side verification script that needs NodeJS and has its own dependencies. Is there a best practice for bundling this external script to go alongside an extension, so that I could, for example, during my extension's development run yarn build and end up with a standalone dist of my script so that the Flarum server installing my extension only needs Node, and does not need npm/yarn to also install its dependencies?

Here's the offending code: https://github.com/Swader/flarum-web3address/blob/master/src/Listener/SaveUserWeb3Address.php#L28

Note that I must do this because there are no crypto functions in PHP for the stuff I'm trying to do. Once they're built, I'll change it all to be PHP-native.

clarkwinkelmann

Swader Flarum comes bundled with a default webpack configuration with presets for extension development. You can modify that default webpack configuration to suit your needs.

Or you can have a separate folder where you manage your dist file compilation separately from Flarum's webpack configuration. There's no limit to what you can include in your extension bundle on Packagist.

As an inspiration here's how I used webpack's copy-plugin together with Flarum in the past https://github.com/clarkwinkelmann/flarum-ext-emojionearea/blob/0.2.2/js/webpack.config.js

Swader

Perfect, thanks. Right now I solved it by:

running browserify with npx during build.
committing the built file.
using the built file from within the exec script if in prod, using the source file if in debug mode.

Should work just fine now on any machine with NodeJS.