he/him 
Feature was prompted after spending way too much time debugging parser tests.
Show this thread
The Rome testing framework will give you a stack trace when a test worker becomes unresponsive due to an infinite loop in a test. Works by using the V8 inspector protocol to trigger the debugger and dump the paused call frames.pic.twitter.com/h3I3aBESG1
-
-
-
Could also probably add the ability to drop into a CLI REPL automatically, or keep the debugger paused to allow you to connect via Chrome devtools to do whatever.
Show this thread
End of conversation
New conversation -
-
-
Why’s the error message pointing at the “u” in “function”?
-
0 vs 1 indexed columns
V8 don't use them consistently - 4 more replies
New conversation -
-
-
I'm finding it awkward to refer to individual pieces of Rome. "Rome testing framework" doesn't exactly roll off the tongue. I'm thinking of calling pieces, rome.lint, rome.test, rome.compile, rome.bundle etc.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
was it build in a day?
-
This feature was, yeah
- 2 more replies
New conversation -
-
-
You've probably been asked already, but was it built in a day? ;)
- 3 more replies
New conversation -
-
-
That’s cool! I am curious though, I’d love to see a poll of how many JS developers accidentally wrote an infinite loop in even the last year? I see a fair amount of code, I haven’t seen a while loop in a while (ha). I do see setTimeouts used without clears way more than I should
-
I think any developer who writes stateful code will run into infinite loops
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.