You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm usign concurrently for my azure fucntions node.js project. I need to compile my typescript and run the azure functions at the same time.
here is my package.json script "start": "concurrently --kill-others \"tsc -w\" \"func start\"",
Problem is that randomly the prefix is missing from the logs. Which misalign my data in the logs which can be pretty annoying sometimes:
I tried to remove the prefix (since I don't really need it) but setting it to an empty string brings back the [0] and [1]. I also tried setting it to a radom caracter like "-" but still have the same issue
Expected Behavior:
Do not skip some prefix
Be able to remove the prefix by setting it to empty string
Environment
Node.js v18.19
The text was updated successfully, but these errors were encountered:
Thanks for the report.
I'm pretty sure that your command must be writing multiple lines without a line break at the end, e.g. process.stdout.write('hello\nworld').
Description:
I'm usign concurrently for my azure fucntions node.js project. I need to compile my typescript and run the azure functions at the same time.
here is my package.json script
"start": "concurrently --kill-others \"tsc -w\" \"func start\"",
Problem is that randomly the prefix is missing from the logs. Which misalign my data in the logs which can be pretty annoying sometimes:
I tried to remove the prefix (since I don't really need it) but setting it to an empty string brings back the [0] and [1]. I also tried setting it to a radom caracter like "-" but still have the same issue
Expected Behavior:
Environment
Node.js v18.19
The text was updated successfully, but these errors were encountered: