-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
Needs Triageneeds an initial reviewneeds an initial review
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When running nested npm commands like implicit pre and post scripts (pretest, prepack, preinstall...), they are run on new spawned processes, with the only reference to where they start by the process banner, but there's no indication of where they end or their relationship, since output is flat.
Expected Behavior
I would like that when a npm command is exec as direct or indirect result of a previous npm command, that its output gets indented, so it's easier to see where they start and end and who's its parent npm process. To do it, we would need to do:
- detect we are running as a nested
npmcommand, if not proceed as usual. - use https://nodejs.org/api/tty.html or https://nodejs.org/api/readline.html to create a virtual TTY where to run the command, instead of using
inherit. Also handle theresizeevent, and maybe mimic someway the commands they are not running on a TTY if the parent process doesn't does it. - process the output to the
stdoutandstderrof the virtual TTY, and indent it for each newnewlinethat arrives
Steps To Reproduce
No response
Environment
- npm: 9.6.7
- Node: v20.3.1
- OS: Ubuntu Linux 23.04
- platform: x86_64
Metadata
Metadata
Assignees
Labels
Needs Triageneeds an initial reviewneeds an initial review