MS Edge implements tracepoints. In their words (MSDN): "A tracepoint is a breakpoint with a custom action associated with it. When the tracepoint is hit, it causes the debugger to perform the specified action instead of ... breaking program execution."

TLDR, it's a breakpoint that doesn't break, but instead console.log's (among other things).

It's a common use case of conditional breakpoints to console.log things to determine code paths without pausing on every execution, but existing workarounds are cumbersome. (From searching stackoverflow, most people modify source and add console.log manually, which is hard to track and tedious).

Tracepoints that just logged "Hit tracepoint #xxx" would be useful for debugging.