support for `--watch`
See original GitHub issueThe mocha option --watch
currently doesn’t seem to do anything. Could that be added? Besides that this is really great!
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Apple Watch Support
Learn how to set up and use your Apple Watch. Find all the topics, resources, and contact options you need for Apple Watch....
Read more >Service & Support - CITIZEN WATCH Global Network
Service & SupportCITIZEN WATCH Global portal site.
Read more >Apple Watch Series 7 - Support Overview - Verizon
Find all Watch Series 7 Support information here. Learn how to activate, set up features & troubleshoot issues with our FAQs, how-to guides...
Read more >Contact Us - Google Pixel Watch Help
Google Pixel Watch Help · Sign in. Send feedback on... This help content & information. General Help Center experience. Next. Help Center ·...
Read more >Get Apple Watch Support - AT&T Wireless Customer Support
Apple Watch bands are available in a variety of styles and sizes. First, choose a case size and band style to see which...
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
It’s been some years since this was closed. I think it can be worth a new discussion whether this should be included in
electron-mocha
. mocha decided to keep watch since it’s widely used and appreciated by the community.How much would it take to implement this functionality in electron-mocha? If it’s wanted I may put some time in doing a PoC for this.
I did a quick investigation, it seems that
watch
is not handled by the mocha library itself, but by the CLI tool around it see, instead of here. (surprisingly this also holds for features likecompilers
). This makes it impossible to cleanly reuse the functionality, so it makes sense to me that you don’t want to support this scenario as it would indeed introduce additional maintenance.Will search for another, less optimal, solution