sometimes a step over steps in - possibly a bug in node

[davidmarkclements]

on occasion going next result in a step-in (occurs often around require statements)

however this same behavior can be observed in node-inspector, so either there's a shared misunderstanding of the v8 debugging protocol or there's a bug in node core