unable to test when employing template strings

[jmonster]

I'm enjoying some ES6 fanciness, e.g:

callback(null, `https://${host}${path}`, headers);

However, Lab can't process this:

> node ./node_modules/.bin/lab --timeout 5000 --lint --coverage

/Users/johnny/Documents/lanai/node_modules/lab/node_modules/espree/espree.js:5435
        throw e;
              ^
Error: Line 12: Unexpected token ILLEGAL

So I've altered my package.json to pass in the necessary --use_strict argument that is needed to unlock this feature:

"scripts": {
    "test": "node --use_strict ./node_modules/.bin/lab --timeout 5000 --lint --coverage",
    "start": "node --use_strict index.js"
  }

But once I do this, I encounter a new problem:

> node --use_strict ./node_modules/.bin/lab --timeout 5000 --lint --coverage

/Users/johnny/Documents/lanai/node_modules/lab/lib/coverage.js:248
        __$$labCov = {
                   ^
ReferenceError: __$$labCov is not defined

Of course if I drop --coverage, everything runs to completion just fine.. thoughts?

[jmonster]

Hey @geek thanks for taking a look at this, but I'm still having the issue -- although without any mention of __$$labCov:

uku ➤ npm test                                                                                                                                                  git:master*

> uku@0.0.1 test /Users/jdomino/Documents/heroku/uku
> lab --timeout 5000 --lint --coverage

/Users/jdomino/Documents/heroku/uku/node_modules/lab/node_modules/espree/espree.js:5435
        throw e;
              ^
Error: Line 12: Unexpected token ILLEGAL

If I simply remove all usage of template strings in my code [by commenting them out], this command runs to completion just fine.

[geek]

@jmonster I think we will want to change our options when we call espree to be tolerant of parser errors. I will log an issue

[Marsup]

@geek This is probably more a matter of enabling espree ES6 feature here.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.