lint-stage doesn't print any task internal console outputs.
See original GitHub issueDescription
I would like to see the full output generated by the npm scripts I have configured in the “lint-staged” section. At the moment, I can only see the output generated by lint-stage itself but nothing from the subtasks.
Steps to reproduce
package.json
"lint-staged": {
"package-lock.json": [
"node scripts/myCustomScript.js"
],
},
myCustomScript.js
console.log('This never gets printed');
Debug Logs
expand to view
COPY THE DEBUG LOGS HERE
Environment
- OS: Windows 10
- Node.js: 11.4.0
lint-staged
: 8.1.0
Issue Analytics
- State:
- Created 5 years ago
- Reactions:14
- Comments:7
Top Results From Across the Web
Using lint-staged, husky, and pre-commit hooks to fail fast and ...
This pipeline is triggered on every push and pull request, ... and printing the linter's output to the console to allow manual fixes...
Read more >No multiprocessing print outputs (Spyder) - Stack Overflow
Now it is clear that the console only seems to print the info function, but not any output of the f function (which...
Read more >Release and Version History — pipenv 2022.12.20.dev0 ...
virtualenv creation no longer uses --creator=venv by default; introduced two environment ... Fix regression: pipenv does not sync indexes to lockfile.
Read more >Bitcoin Core 0.17.0
Bitcoin Core should also work on most other Unix-like systems but is not ... He constructs a PSBT that contains certain inputs and...
Read more >failed to load parser '@angular-eslint/template-parser' - You.com
Here is my issue: When I run "ng test" with ChromeHeadless on my local machine, all the test are triggered correctly and I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Piping exaca > process.stdout in execLinter function from resolveTasksFn solves the issue for me but not sure about the side effects it could generate.
return execa(bin, binArgs, { ...execaOptions })**.stdout.pipe(process.stdout);**
It’s my fault, I just called
process.exit()
in my internal scripts, change toprocess.exitCode
do help,after that all my console output displayed completely.