zeek: Enable building of JavaScript integration

[bbannier]

With #256036 node now installs its shared library as well. If available the library is detected by the Zeek build to enable Zeek's JavaScript integration, and this patch makes the integration available deterministically.

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[daeho-ro]

Isn't it a build dependency? and also want to know node version 25 can be used or not.

[bbannier]

Thanks for taking a look @daeho-ro.

Isn't it a build dependency?

The formula needs it both as a build dependency to pull in headers, and runtime dependency since the zeek executable will link libnode dynamically.

and also want to know node version 25 can be used or not.

I tried an unpinned node dependency first. This failed on e.g., macos-14 since the node-25 headers use C++20 features not available with the system compiler. I can switch this to use a Homebrew-managed clang instead, but I figured just depending on node@24 would be a lighter approach.

[bbannier]

@daeho-ro Does that makes sense, or do you want me to switch the formula to compilation with clang so it can depend on an unpinned node?

[bbannier]

Is there anything I can do to get this moved forward?

[bbannier]

@daeho-ro sorry for the direct ping. Can you tell me what else would be needed here to get this unblocked?

The way the formula is currently in main, Zeek's JavaScript feature will not be consistently available (I suspect this has to do with whether some other job left node on the bottle build host).

[daeho-ro]

I think this is fine for now, and sorry for late response I was busy on company things and just forgot this.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.