If npm/pypi/etc dependencies contains native binaries, should we rebuilt that?

[rinsuki]

TypeScript 7.0.0 replaced their compiler implementation to new Go-based one, from old TypeScript (self-hosted) one.

because of this, now typescript formula just pulling their official native binaries:

$ file /opt/homebrew/opt/typescript/libexec/lib/node_modules/typescript/node_modules/@typescript/typescript-darwin-arm64/lib/tsc
/opt/homebrew/opt/typescript/libexec/lib/node_modules/typescript/node_modules/@typescript/typescript-darwin-arm64/lib/tsc: Mach-O 64-bit executable arm64

but I saw this policy:

https://docs.brew.sh/Acceptable-Formulae
It must either build from source or install portable, platform-independent output such as Java bytecode.

since It's native Mach-O (or ELF on linux) binary, typescript formula does not meet this policy anymore. It sounds like we would need to compile tsc binary from the source, instead of just pulling official binaries, but should that happen?

note some other formulae have same problem, e.g. oxfmt:

$ file /opt/homebrew/opt/oxfmt/libexec/lib/node_modules/oxfmt/node_modules/@oxfmt/binding-darwin-arm64/oxfmt.darwin-arm64.node 
/opt/homebrew/opt/oxfmt/libexec/lib/node_modules/oxfmt/node_modules/@oxfmt/binding-darwin-arm64/oxfmt.darwin-arm64.node: Mach-O 64-bit dynamically linked shared library arm64

[SMillerDev]

Yes we should, although that is generally very difficult to do for npm packages so we don't always manage. A pull request to this extent would be very welcome.