Clinic doesn't work with Powershell
See original GitHub issueHi. I have a lot of deprications during npm installation: https://i.imgur.com/c7UFe45.jpeg
Further…
clinic doctor -- node server.js
or
clinic doctor --autocannon [ / ] -- node ./server.js
And…nothing, screen: https://i.imgur.com/700N9aQ.jpeg
P.S. I use Node 17, Win10
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
PowerShell Clinic – Cimitra
PowerShell Scripting Introductory Clinic. A introductory guide to PowerShell Scripting – PowerShell Version 7 is used in this clinic.
Read more >PowerShell is not recognized as an internal or external ...
Cause. This is caused by the user (or system) PATH environment variable not containing the directory where the PowerShell executable resides.
Read more >Powershell stopped working Windows 10 - Microsoft Community
"powershell has stopped working. A problem did that the program stopped working correctly. The program has been shut shut down and you will ......
Read more >Problems you solved at work with powershell - Reddit
Hi, was trying to see some real-world examples of powershell being applied, so that I could try to tackle the issues myself and...
Read more >Best Fixes: PowerShell Not Opening on Windows 11 - MiniTool
Way 1: Restart Your Computer; Way 2: Run an SFC Scan; Way 3: Create a New User Account; Way 4: Use another Way...
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
@Arimanecro It seems to be an issue with PowerShell itself. Several resources on the web indicate this behaviour.
A double hyphen instructs PowerShell to treat everything coming after as literal arguments rather than options. To avoid that behaviour you can either quote (“–”, ‘–’) or escape (`–) the double hyphen.
This works for me in PS:
clinic doctor '--' node server.js
cc @RafaelGSS : can you remove the “bug” label?.. maybe we can refer to this PS behaviour in the docs.
Hi @Arimanecro, could you check if some of those approaches work?
clinic@9