I'd like to be able to run interactive commands.

[AlbertClo]

Sometimes a command might need some interaction from time to time. E.g. when I'm running Storybook, and the default port for it is occupied, it asks if you want to run it on another port.

Currently I don't see a way to tell Storybook to continue running.

[simonhamp]

You have a couple of options here with Storybook:

1. You could be explicit about the port in your command. I haven't tried this but something like may work e.g. npm run storybook -- -p6007
2. You can try passing the -y flag which should answer yes to any prompts: npm run storybook -- -y

Note the -- before passing Storybook-specific flags/parameters - this is how the shell & npm know to pass these down to storybook itself. Otherwise you'd have to write out the full command from your package.json->scripts->storybook

[AlbertClo]

Yeah, I could do that. But this just an example of a general problem. There are many other reasons to want to be able to drop into interactive mode.

[aarondfrancis]

Working on this in #4!

[antoniofrignani]

Another use case for this is to have a Tinker tab opened to test simple commands directly from within it.

Actually, if i try to add a Tinker tab, it dies poorly 😅