Ways of configuring a CLI tool:
1️⃣ Command-line options
2️⃣ Config file
3️⃣ Env vars
4️⃣ Comments in input files (e.g. eslint, pretter)
Huge difference. In 3 & 4 you don't need to know hardly anything about how the process is spawned, etc. It "just works"
1️⃣ Command-line options
2️⃣ Config file
3️⃣ Env vars
4️⃣ Comments in input files (e.g. eslint, pretter)
Huge difference. In 3 & 4 you don't need to know hardly anything about how the process is spawned, etc. It "just works"
I think this is a big part of why it's so much easier to use console.log vs. a debugger. Debugger often requires you to modify the way the process is launched. Adding a console.log / printf just works, even if your process is remote (e.g. CI), spawned by the test framework, etc.
https://twitter.com/dubroy/status/1457952580504543233 ∙ Archived on 2025-03-28.