Same command resulting in different outputs

[ahmedragab20]

I'm encountering a bug where running the npm run test or npm run test:coverage results in incorrect output in Ghostty.

here's the Hyper version (Github Action CI/CD pipeline results in the same output as well):

Ghostty:

[edrozenberg]

It's not clear from your screenshots what is incorrect or expected to happen. A description and drawing a box around the problem areas would help. What is good and what is bad here, is it the formatting, the data output, does Ghostty show it differently than which other app(s) (kitty/alacritty/wezterm/gnome term/kde term/xterm)?

[ahmedragab20]

Actually, the issue is straightforward. I run npm run test command in different terminals when I run it on hyper or vscode terminal or even in the pipeline all tests pass but when I rerun the same command on Ghostty it results in what you see in the screenshot tests do not pass

[pluiedev]

Unless your test suite somehow decides that it only wants to work under a certain terminal, I'd say this is not a Ghostty issue. (Except of course if you're talking about something else entirely, like a visual bug)

[ahmedragab20]

I didn’t entirely get what you said, but I don’t think it’s terminals’ problem because it runs perfectly in the pipeline

[pluiedev]

Unless your test suite has to send characters directly to the terminal or has to detect for features in the terminal to work, then it's not a terminal issue.

[00-kat]

Sanity check: are you running the same command in both screenshots?

[ahmedragab20]

Exactly yeah, it’s the same command, the same codebase, on any other terminal the tests will pass, oh Ghostty the command will result in what you see in the back screenshot attached above

[av223119]

Wild guess: your "other" terminals launches a "login shell" which sets up environment needed for the command to succeed, while ghostty does not. Please compare env output in both cases.

[rhodes-b]

that is very wrong, on macos ghostty starts each shell as a login shell
https://ghostty.org/docs/help/macos-login-shells

[av223119]

Doesn't really matter -- could be vice versa. It's a convention to source non-login config from the login one, but who knows OP's setup. My point about env stands.

[ahmedragab20]

@av223119 I think it's something completely different.. the command works everywhere even in the GitHub action pipeline, only Ghostty gives me this error (shown in the pic above) and that has not been the case in the previous version, it was just working fine.

and the WILD thing is that I don't know why the hell it acts this way in this very specific senecio, and works perfectly fine with everything else?????! 🤦🏻‍♂️

[mitchellh]

Moving to Q&A. This is definitely something environmental that npm or your tests are doing. Something somewhere is utilizing an environment variable or something that is differing.