tree-sitter-swift @0.3.4: Failed to run `node`: Os { code: 2, kind: NotFound, message: "No such file or directory" }

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/ports-12_arm64-builder/builds/80304/steps/install-port/logs/stdio

thread 'main' panicked at 'Failed to run `node`: Os { code: 2, kind: NotFound, message: "No such file or directory" }', cli/src/generate/mod.rs:176:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Command failed: /opt/local/bin/tree-sitter generate
Exit code: 101

[ryandesign (Ryan Carsten Schmidt)]

The same problem affects 0.3.5 and 0.3.6. Builds fail on all buildbot workers and on my system as well.

[ryandesign (Ryan Carsten Schmidt)]

Looks like this is a bug in tree-sitter-cli, which apparently depends on the existence of a node binary?

[amake (Aaron Madlon-Kay)]

No, it's not a bug; the tree-sitter CLI tool shells out to node:

​https://github.com/tree-sitter/tree-sitter/blob/25d9c989ebdc53dbad3852317c5b45228ff012e4/cli/src/generate/mod.rs#L171

So the tree-sitter-cli port needs a nodejs port as a runtime dependency.

[amake (Aaron Madlon-Kay)]

​https://github.com/macports/macports-ports/pull/17967

[Aaron Madlon-Kay <aaron@…>]

In ca9ca0e68ef28c5471745f11d3e5dafcb95e5b2e/macports-ports (master):

tree-sitter-cli: add NodeJS runtime dependency

See: #66595

[amake (Aaron Madlon-Kay)]

This should be fixed. Am I able to trigger a rebuild?

[ryandesign (Ryan Carsten Schmidt)]

I've scheduled rebuilds of tree-sitter-swift on 10.9 and later.