JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Being able to run tests directly from vanilla Node is an essential simplification IMO. node test.js I hope more people begin to value this when selecting a testing approach.
What do you expect that to do? Actually run your tests? Or just execute that file with no errors?
I expect test output for that one file... I come from the cross-language tap ecosystem, where direct test output is defined protocol that's consumed by test runners. Because it's a protocol, I've written tap tests in everything from C to MySQL.
Ahh. I guess I come from (and helped create) a world where when I want to run my JS, it has to be processed anyway, so there’s always at least one level of indirection.
It should run the tests in that file, and then set the exit code to express whether all tests passed. The key is that when I'm confused about a test's behaviour, it gives me a way to debug a test in the most minimal and isolated manner. For example: node --inspect-brk test.js
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
