Prompts doesn't work in global packages with Git Bash or Windows CMD about prompts

[tunnckoCore]

What you mean with "in global packages"? I can't got it. ;]

[FoRVaiS]

Sorry, i was just about to update my post regarding that.

I've published the sample code in a private npm repository and installed globally: npm install -g local-prompts-global.

The package also has a bin command:

"bin": {
    "prompts-test": "index.js"
 }

Running prompts-test will result in a failing prompts application

[tunnckoCore]

Huh. And locally works? Is it working for the other type of prompts?

I have strong feeling, looking on the stack trace, that it may be because #19

[tunnckoCore]

Actually it isn't because of #19.

Possible fix would be

this.in.setRawMode = this.in.isTTY ? this.in.setRawMode : () => {}

So we won't think for it in other places.

[FoRVaiS]

Using Visual Studio Code (VSC) Terminal, set to Git Bash, I can use Prompts perfectly:

[tunnckoCore]

Can you try to replace this line

prompts/lib/elements/prompt.js

Line 39 in b6126d3

this.in.setRawMode(false);

with

      if (this.in.isTTY) {
        this.in.setRawMode(false);
      }

so we can verify more faster if it is only that thing. Because it not make sense to me since it works locally, but this bug is seen in other big projects too.

[FoRVaiS]

I no longer get the exception.
Prompts.text responds correctly and then duplicates its line.
Prompts.select remains un(scrollable)?
At the end, the application hangs, unable to kill the process via CTRL+Z and CTRL+C.

EDIT: I've now realized that the 'duplicated' line is actually intentional. The previous line before it failed to update/disappear

[tunnckoCore]

Ah. Okey, thanks! We can continue work on #36 then.

CTRL+Z and CTRL+C.

It's another problem - #27

[tunnckoCore]

Sorry for bothering you, but.. What about adding else to the previous given if

      else {
        this.clear()
      }

Strongly believe that i would fix the problem with double lines, because this.clear is available after the this.render call, which in turn is called before the this.close() from the submit().

[FoRVaiS]

I've already shut my computer off, I'll definitely try this tomorrow.

[tunnckoCore]

Okey thanks anyway! 🐝 It's not comfortable in such situations when no tests and/or Windows specific things. Also, it's a bit tricky to test CLI prompts :D

[terkelg]

Right, make sense to wrap the setRawMode in close in an if-statement too. So the issue is down to prompts.select not being scrollable on windows?

[FoRVaiS]

The only two functional issues I have come across so far is

1. Unscrollable prompts.select
2. Application hanging

Issue 2 might be related to a hanging stdin but my experience on I/O is extremely limited so I could be very wrong :X