Support single-file executables via bun build --compile

[Jarred-Sumner]

This unblocks using tree-sitter-typescript in single-file executables

This is the same as tree-sitter/node-tree-sitter#230, except specifically for tree-sitter-typescript instead of tree-sitter.

node-gyp-build performs runtime checks for figuring out where the .node file is, but those runtime checks are difficult for static analysis to figure out where the .node file is. If we can rely on the prebuild to exist, we can use a template string and Bun will inline the process.platform, process.arch, and process.versions.bun fields within --compile.

Related PRs:

• Support compiling single-file executables via bun build --compile node-tree-sitter#230
• Inline process.versions.bun in bun build --compile oven-sh/bun#14940
• Fix napi property methods on non-objects oven-sh/bun#14935
• Implement NAPI type tagging oven-sh/bun#14915

[amaanq]

@Jarred-Sumner do you mind submitting a PR to update the template file pointed out here? This will allow anyone who creates a grammar automatically have the bun check

[Jarred-Sumner]

@amaanq is there a way to know what the package name is statically? since node-gyp-build includes the package name in the file name

[amaanq]

Yeah, when the bindings are initialized or updated there are few "variables" that are replaced with the parser's actual name, e.g. PARSER_NAME gets replaced with whatever the parser name is in the tree-sitter json config. So you could use this to update the template