Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading to 7.2.0 throws SyntaxError (up to node v3.3.1) #281

Closed
hbaqai opened this issue Dec 7, 2016 · 3 comments
Closed

Upgrading to 7.2.0 throws SyntaxError (up to node v3.3.1) #281

hbaqai opened this issue Dec 7, 2016 · 3 comments
Labels

Comments

@hbaqai
Copy link

hbaqai commented Dec 7, 2016

#193 seems to have shown up again starting in 7.2.0. Using node v0.12.17 gives the following error:

>> const Hoek = require('hoek');
>> ^^^^^
>> SyntaxError: Use of const in strict mode.
>>   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 (/Users/hashir/Projects/opentok-node/node_modules/grunt/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
>>   at Function.Module._load (module.js:310:12)
>>   at Module.require (module.js:365:17)
>>   at require (module.js:384:17)
>>   at Object.<anonymous> (/Users/hashir/Projects/opentok-node/node_modules/jsonwebtoken/sign.js:1:73)
>>   at Module._compile (module.js:460:26)
>>   at Object.Module._extensions..js (module.js:478:10)

various other errors show up if I upgrade to a node version up to and including v3.3.1. Upgrading to node v4.0.0 and above seems to make the errors go away.

@hbaqai
Copy link
Author

hbaqai commented Dec 7, 2016

For now, I've worked around the problem by using:

"jsonwebtoken": "~7.1.x"
instead of

"jsonwebtoken": "^7.x.x"

in my package.json

@hbaqai hbaqai changed the title Upgrading to 7.2.0 throws SyntaxError (upto node v3.3.1) Upgrading to 7.2.0 throws SyntaxError (up to node v3.3.1) Dec 7, 2016
@ziluvatar ziluvatar added the bug label Jan 13, 2017
@ziluvatar
Copy link
Contributor

@hbaqai this should work now with last version, can you check?

@ziluvatar
Copy link
Contributor

@hbaqai I'm closing the issue, be free to open it if you find it happening again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants