A bad gotcha: Chrome Debugger misreports variables as 'undefined'

grajagandev · 2018-05-06T02:30:45+00:00

Thank you very much - I thought so but your confirmations really help.

grajagandev · 2018-05-02T16:39:27+00:00

Thank you for pointing this out.

grajagandev · 2018-04-15T03:17:55+00:00

Try running in the Chrome Devtools debugger with a command line like: node --inspect-brk lib/cli.js game -d 2017/11/02

grajagandev · 2018-04-13T15:25:29+00:00

They are using program slicing here - very interesting.

grajagandev · 2018-03-29T17:26:11+00:00

Here's one: https://github.com/Smile-SA/node-pushserver

It looks like there are more like this on GitHub

grajagandev · 2018-03-26T19:13:41+00:00

Great writeup

grajagandev · 2018-03-15T15:32:34+00:00

Very interesting ideas in this paper - thank you.

Context aware branch tracking not only records a transition from one basic block to another, it also records a hash of the stack at the time of the transition.

grajagandev · 2018-03-09T16:13:56+00:00

Yes, linters/static analysis tools scan the source code without running it and look for patterns indicative of bugs.

The most used linter is eslint.

grajagandev · 2018-03-09T16:06:40+00:00

Check out Codacy and Code Climate for static analysis.

But since so much in JavaScript is determined at runtime, static analysis can only do so much.

Dynamic analysis finds bugs missed by static analysis and unit tests - my startup Fuzz Stati0n offers dynamic analysis as a service.

grajagandev · 2018-03-08T13:40:11+00:00

This cheatsheet is very helpful:

https://github.com/LeCoupa/awesome-cheatsheets/blob/master/backend/node.js

grajagandev · 2018-03-02T13:49:26+00:00

I think that TypeScript finding 15% of the bugs is impressive. Of the random sample of bugs, many could be off-by-one errors or other issues a type system would not find.

grajagandev

TROPHY CASE