search

Eugeny / tabby

A terminal for a more modern age
https://tabby.sh
MIT License
58.64k stars 3.37k forks source link

Running npm commands doesn't work in tabby #5438

Open kishikaisei opened 2 years ago

kishikaisei commented 2 years ago

Describe the problem: When running inside of a pwsh a command such as npm install or npm start instead of running it normally like in regular pwsh, it doesn't in tabby (it works fine while running cmd inside of tabby), it shows this instead:

USERNAME in NGAARStats on   master ❯ npm install
reset user data to C:\Users\USERNAME\scoop\apps\tabby\current\data

To Reproduce: Run npm install on npm project folder (angular project in my case)

OS: Windows 11 Tabby version: 1.0.168

kishikaisei commented 2 years ago

Tried installing the latest version 1.0.169 instead of using scoop there is no feedback:

USERNAME in NGAARStats on   master ❯ npm start 

USERNAME in NGAARStats on   master ❯ npm install

USERNAME in NGAARStats on   master ❯
TylerTemp commented 1 year ago

Not sure it was the same, I meet the same problem. My env is: Tabby + cygwin. For me, the problem is that tabby has some issues with stdout buffering. For example, if a program print stuff, it works fine. If a program like npm/yarn behaves like "curses". It'll give no output.

Uninstall, reboot, reinstall, reboot does not work for me. Actually, I end up with a system reinstall... Not a helpful solution, but maybe there is some way to fix the output buffer?

flerouwu commented 5 months ago

I fixed this issue by disabling Set Tabby as %COMSPEC% in Settings > Terminal (at the bottom). This also affects the code.bat file for VSCode.