You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
~/.config/fish/functions/_tide_item_node.fish (line 3):
node --version | string match -qr "v(?<v>.*)"
^~~^
in function '_tide_item_node'
called on line 15 of file ~/.config/fish/functions/_tide_2_line_prompt.fish
I have started using the mise tool to manage node versions, and when entering a directory with a node version that's not yet installed, it automatically fetches it. But during that time, the node command is technically not available for Tide to run, resulting in the above error. However the main issue here is that Tide tries to run node even if it's not available on the system.
Steps to reproduce
Ensure node command not available.
cd into a directory that includes a package.json file.
Describe the bug
I have started using the mise tool to manage node versions, and when entering a directory with a node version that's not yet installed, it automatically fetches it. But during that time, the
node
command is technically not available for Tide to run, resulting in the above error. However the main issue here is that Tide tries to runnode
even if it's not available on the system.Steps to reproduce
node
command not available.package.json
file.Screenshots
N/A
Environment
Output of
tide bug-report
:Additional context
Just to say thanks for all the work on this prompt! It's the best one I've seen on any shell; love the async stuff 🤓
The text was updated successfully, but these errors were encountered: