Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SyntaxError: Unexpected token =

See original GitHub issue

When I try to use your example in my local node v5.12.0 instance running on Gentoo Linux, I get the following error:

/home/manny/hs110q/node_modules/hs100-api/index.js:16
function Hs100Api (config = {}) {
                          ^

SyntaxError: Unexpected token =
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/manny/hs110q/index.js:3:18)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)

The example I used was:

'use strict';

const Hs100Api = require('hs100-api');
const hs = new Hs100Api({host: '192.168.0.11'});
hs.getSysInfo().then(console.log);

Issue Analytics

State:
Created 7 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

plasticrakecommented, Jul 17, 2016

Thanks for your input @bartdorsey. I’ve made changes to be compatible for node v4 (tested using 4.4.7)

1reaction

plasticrakecommented, Jul 14, 2016

Ah yes, this is syntax that requires Node 6. I’ll update the package.json to show this dependency. Are you able to use Node 6? It wouldn’t take long to make it compatible with 5 if anybody needs it.