[BUG]: bun exec varlock init doesn't work, but it works with npm

[ticktricktrack]

varlock version

0.9.1

Steps to reproduce

Follow the tutorial to get started with NextJS https://varlock.dev/integrations/nextjs/:

bun add @varlock/nextjs-integration varlock

Then try to init varlock

project-folder% bun exec -- varlock init
bun: command not found: varlock

What is expected?

🧙 Hello and welcome to Varlock 🔒🔥✨

What is actually happening?

bun: command not found: varlock

System Info

MacOS, Node v25.2.1, Bun latest v1.3.9

Any additional comments?

npm exec -- varlock init works just fine

[philmillman]

Yeah I can repro that. Thanks for the report @ticktricktrack. For now use bun run ... or bunx ... and we'll fix or update the docs accordingly.

[philmillman]

@theoephraim IIUC this is happening because the bundled cli includes #!/usr/bin/env node which means that bun exec requires node to be available in the PATH. We can either update this or update the docs to mention bunx instead (or probably both).

[ticktricktrack]

bunx would match most other libraries docs I've seen

[theoephraim]

yeah I did a little digging and it seems like what we are doing is considered best practice, so probably just a docs change is the right move. Thanks for letting us know.