env: node: No such file or directory

[lgyhero]

I'm following the tutorial: Build an iOS Application: https://docs.bazel.build/versions/master/tutorial/ios-app.html, and failed in step: 'Run and debug the app in the simulator'.

Tulsi was built and installed successfully, but error occurs when I'm creating a new project:

The error says: env: node: No such file or directory.

I'v already installed Node.js on my Mac, here is the node version from Terminal console.

Could you please give some advice or solutions? thanks.

[keith]

What's the output of which node? I imagine it's somewhere tulsi (and all apps) don't see. If you quit tulsi and run open -a Tulsi from terminal that might work

[lgyhero]

What's the output of which node? I imagine it's somewhere tulsi (and all apps) don't see. If you quit tulsi and run open -a Tulsi from terminal that might work

@keith Here is which node output:

I tried run Tulsi with open -a Tulsi from terminal, and the same error occurs:

[2:15:45 PM](3): Running /usr/local/bin/bazel info '--override_repository=tulsi=/Users/XXX/Library/Application Support/Tulsi/0.20210318.88/Bazel'
[2:15:45 PM](3): Bazel command info:
/usr/local/bin/bazel info '--override_repository=tulsi=/Users/XXX/Library/Application Support/Tulsi/0.20210318.88/Bazel'
Exited with code 127

env: node: No such file or directory

[2:15:45 PM](0): Failed to query information about the Bazel workspace. Bazel exited with code 127 [Details]: env: node: No such file or directory

[2:15:45 PM](0): Was not able to extract the execution root from the workspace. This is a Tulsi or Bazel bug, please report.
[2:15:45 PM](3): Running /usr/local/bin/bazel --max_idle_secs=60 query '--override_repository=tulsi=/Users/XXX/Library/Application Support/Tulsi/0.20210318.88/Bazel' --announce_rc --noimplicit_deps --order_output=no --noshow_loading_progress --noshow_progress 'kind(rule, ios-app:all)' --output xml
[2:15:45 PM](3): Bazel command info:
/usr/local/bin/bazel --max_idle_secs=60 query '--override_repository=tulsi=/Users/XXX/Library/Application Support/Tulsi/0.20210318.88/Bazel' --announce_rc --noimplicit_deps --order_output=no --noshow_loading_progress --noshow_progress 'kind(rule, ios-app:all)' --output xml
Exited with code 127

env: node: No such file or directory

[2:15:45 PM](0): Failed to retrieve information about the Bazel workspace. This usually means that the contents of a BUILD file are incorrect or flags are missing. Read the message log carefully for details. [Details]: 

[Jacky-LinPeng]

I get same problem： ` 4:42:11 PM: Running /usr/local/bin/bazel info '--override_repository=tulsi=/Users/mac/Library/Application Support/Tulsi/0.20220209.88/Bazel' 4:42:11 PM: Bazel command info: /usr/local/bin/bazel info '--override_repository=tulsi=/Users/mac/Library/Application Support/Tulsi/0.20220209.88/Bazel' Exited with code 127

env: node: No such file or directory

4:42:11 PM: Failed to query information about the Bazel workspace. Bazel exited with code 127 [Details]: env: node: No such file or directory

4:42:11 PM: Was not able to extract the execution root from the workspace. This is a Tulsi or Bazel bug, please report. 4:42:11 PM: Running /usr/local/bin/bazel --max_idle_secs=60 query '--override_repository=tulsi=/Users/mac/Library/Application Support/Tulsi/0.20220209.88/Bazel' --announce_rc --noimplicit_deps --order_output=no --noshow_loading_progress --noshow_progress 'kind(rule, ios-app:all)' --output xml 4:42:11 PM: Bazel command info: /usr/local/bin/bazel --max_idle_secs=60 query '--override_repository=tulsi=/Users/mac/Library/Application Support/Tulsi/0.20220209.88/Bazel' --announce_rc --noimplicit_deps --order_output=no --noshow_loading_progress --noshow_progress 'kind(rule, ios-app:all)' --output xml Exited with code 127

env: node: No such file or directory

4:42:11 PM: Failed to retrieve information about the Bazel workspace. This usually means that the contents of a BUILD file are incorrect or flags are missing. Read the message log carefully for details. [Details]: `

~]$ node --version rvm: v14.17.2

[keith]

Thanks for submitting this issue but this tool is being deprecated. Please checkout rules_xcodeproj for a more complete and maintained Xcode integration.