Work in progress fix for #32. I'm opening the PR early to check the approach and ask some questions 😄

So far I have hacked in basic v8 support and tested on Chrome 58. I'll do the other engines and eval tests when i'm happy with the approach.

A few questions about setEvalOrigin. Given this program:

// index.js
function f() {
  return g();
}

function g() {
  return h();
}

function h() {
  try {
    eval(`
function willThrow() {
  return doesNotExist;
}

willThrow();
    `);
  } catch (e) {
    console.log(e.stack);
  }
}

f();

• Which is the "parent" stack frame - eval in index.js or willThrow in <anonymous>?
• Should the parent or child frame have the isEval flag?

The logic in the PR so far is a simple delta from master which has willThrow/index.js as the parent.

Description

Expose inner line and column information for stack frames inside eval code.

Motivation and Context

See #32.

How Has This Been Tested?

So far: one unit test on a stack frame from Chrome 58.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• node_modules/.bin/jscs -c .jscsrc error-stack-parser.js passes without errors
• npm test passes without errors
• I have read the contribution guidelines
• I have updated the documentation accordingly
• I have added tests to cover my changes