Unexpected strict mode reserved word?

[stevenmcastano]

/opt/apps/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:62
    let port = this._tcpServer.address().port;
    ^^^
SyntaxError: Unexpected strict mode reserved word
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/opt/apps/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:11:25)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

Trying a fresh install have my old one of v0.1.1 stopped working.

[KhaosT]

please try update nodejs to a newer version. like v5.0 or later

Best Wishes,
Tian

On Oct 19, 2016, at 1:05 PM, stevenmcastano notifications@github.com wrote:

/opt/apps/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:62
let port = this._tcpServer.address().port;
^^^
SyntaxError: Unexpected strict mode reserved word
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/opt/apps/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:11:25)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
Trying a fresh install have my old one of v0.1.1 stopped working.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #859, or mute the thread https://github.com/notifications/unsubscribe-auth/ABpU4JFFLusJ9cdGQw-MBHF27nIPYG6sks5q1ngBgaJpZM4KbZZ2.

[stevenmcastano]

Upgraded and now everything is running, new issue though with multi cast I think, I’ll open a new ticket.

*SMC

On Oct 19, 2016, at 4:06 PM, Khaos Tian notifications@github.com wrote:

please try update nodejs to a newer version. like v5.0 or later

Best Wishes,
Tian

On Oct 19, 2016, at 1:05 PM, stevenmcastano notifications@github.com wrote:

/opt/apps/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:62
let port = this._tcpServer.address().port;
^^^
SyntaxError: Unexpected strict mode reserved word
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/opt/apps/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:11:25)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
Trying a fresh install have my old one of v0.1.1 stopped working.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #859, or mute the thread https://github.com/notifications/unsubscribe-auth/ABpU4JFFLusJ9cdGQw-MBHF27nIPYG6sks5q1ngBgaJpZM4KbZZ2.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #859 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AF4rND8gGq0-3d-lj4YEg0_14xq12I2gks5q1ng4gaJpZM4KbZZ2.

[ViViDboarder]

I'm getting this same issue using node v7.0.

It's a brand new install that I'm doing inside a container, so there should be little to no other influence. I've looked at the other closed issues that are related to this and they all say to use a newer version of node, so I've bumped mine up to 7.0 but it keeps happening.

Here is my Dockerfile that shows my install command, and here is where the base image is installing node. Is there something else that could cause this error beyond just the version of node? I have very little experience with node myself, so it may be a silly question.

Edit: Actually, tried again and it seems to be working... Not sure what fixed it. If I find out I'll reply.

[stale]

This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[armansa]

I'm having same issue with node 6.12.0