Are there any workaround to bundle argon2 when using bun build --compile?

[deanrih]

So I currently having a test project using Bun and ElysiaJS, specifically for deployment using bun build --compile to produce single executable, it was fine and working as intended until I realize that one of the package (for now it's argon2) is not bundled or can't be found after I removed or just renamed the node_modules into anything else, the server fail to run with this messsage:

$ ./dst/server
2 | var __create=Object.create;var{getPrototypeOf:__getProtoOf,defineProperty:__defProp,getOwnPropertyNames:__getOwnPropNames}=Object;var __hasOwnProp=Object.prototype.hasOwnProperty;var __toESM=(mod,isNodeMode,target)=>{target=mod!=null?__create(__getProtoOf(mod)):{};let to=isNodeMode||!mod||!mod.__esModule?__defProp(target,"default",{value:mod,enumerable:!0}):target;for(let key of __getOwnPropNames(mod))if(!__hasOwnProp.call(to,key))__defProp(to,key,{get:()=>mod[key],enumerable:!0});return to};var __commonJS=(cb,mod)=>()=>(mod||cb((mod={exports:{}}).exports,mod),mod.exports);var __export=(target,all)=>{for(var name in all)__defProp(target,name,{get:all[name],enumerable:!0,configurable:!0,set:(newValue)=>all[name]=()=>newValue})};var __require=import.meta.require;var require_dist=__commonJS((exports)=>{Object.defineProperty(exports,"__esModule",{value:!0});exports.parse=parse2;exports.serialize=serialize;var cookieNameRegExp=/^[\u0021-\u003A\u003C\u003E-\u007E]+$/,cookieValueRegExp=/^[\u0021-\u003A\u003C-\u007E] | ... truncated

error: No native build was found for platform=linux arch=x64 runtime=node abi=127 uv=1 libc=glibc node=22.6.0
loaded from: /path/to/repo/node_modules/argon2

at <anonymous> (/$bunfs/root/server:2:9726)
at load (/$bunfs/root/server:2:8846)
at /$bunfs/root/server:2012:408

Bun v1.2.3 (Linux x64 baseline)

and my guess is since argon2 is a (an?) napi so it couldn't get bundled by bun, even if there's prebuilds .node file in the node_modules directory?

so, are there any workaround to make Bun bundled argon2? I'm planning to experiment with bun c compiler to compile argon2 and see if it actually work and whether it will get bundled or not (if there's someone already tried this, please tell me how it goes)

and for those who asking, why not use Bun.password, which I did, and it works, but only for this test project to test migrating my company's project deployment to use bun build, which happened to use argon2, and the problem is, it can't be migrated into Bun.password, this is the reason:

...

	const passwordVerified = await argon2Verify(hash, plain, {
		secret: Buffer.from(env.SECRET_HASH, "base64"),
	});

...

it uses the secret options on hash and verify function, which Bun.password doesn't have (yet?), so even if I do this

...

        const passwordVerified = await Bun.password.verify(plain, hash, "argon2id");

...

it will result in false, so unless Bun add this feature parity, I can't replace argon2 with Bun.password quite yet

and it seems there's some issue tracking regarding Bun.password options parity

#9074
#9654

To reiterate

Are there any workaround to make Bun bundled argon2? Does using bun c compiler works? Is it dead end (no bun build --compile for now)?

[infrahead]

From a quick glance at the argon2 package, you'd need to modify the source (with bun patch or otherwise) to change the way the .node addons are required. Prebuilds are available so it will definitely work, but for bun build --compile to include them you need simple process.platform and process.arch logic/checks around require statements