zsh: command not found: node

[holy-chen]

Discord username (optional)

No response

Describe the bug

After updating the version, open a new window, and some commands will prompt that they cannot be found.

To reproduce

1. update version: v0.2024.03.05.08.02.stable_01
2. Press cmd + D to create a new window.
3. Enter the command node -v

Expected behavior

It is expected to work normally like the previous version.

Screenshots

Operating system

MacOS

Operating system and version

Sonoma 14.2.1

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0)

Current Warp version

v0.2024.03.05.08.02.stable_01

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

2024-03-07

Additional context

When I use nvm to re-specify the node version, I run node -v to use it normally, but when typing node, it still prompts as an unrecognized command, which is inconsistent with the previous behavior.

However, when I pressed the shortcut key cmd + D again to create a window, the node command still could not be found.

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

No, this same issue happens in Warp and other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[dannyneira]

Hey @holy-chen sorry about this, please run which node and find the path to the binary. Then export that path in your .zshrc file and it should load on startup. echo 'export PATH="$PATH:/path/to/node/bin"' >> ~/.zshrc

Please let us know if that helps!

[holy-chen]

@dannyneira Thank you for the solution, which may be useful for a fixed version. Due to my work, I need to use nvm to switch between different versions of nodes, which causes the path of my node bin file to be always the same, and the version number is dynamic.

[holy-chen]

I encountered the same problem on different terminals, which may be caused by nvm. I created a tracking issue.

[holy-chen]

I encountered the same problem on different terminals, which may be caused by nvm. I created a tracking issue.

The problem has been solved. For details, please check the issue tracked here.