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

When I ran sample watson project through npm run emulator It gives Error SyntaxError: Unexpected token * #100

Open
stephenws opened this issue Oct 22, 2018 · 1 comment

Comments

@stephenws
Copy link

stephenws commented Oct 22, 2018

Hi

I am executing TestMyBot Watson Sample Project through
npm run emulator
It gives me Error : *SyntaxError: Unexpected token '

Logs:

StephenMac:watson Stephen$ npm run emulator

testmybot-sample-watson@1.0.0 emulator /Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson
npm install botium-cli && botium-cli emulator console --convos ./spec/convo --config ./testmybot.json

jsonpath@1.0.0 postinstall /Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson/node_modules/botium-cli/node_modules/jsonpath
node lib/aesprim.js > generated/aesprim-browser.js

testmybot-sample-watson@1.0.0 /Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson
└─┬ botium-cli@0.0.26
└── jsonpath@1.0.0 extraneous (git+https://github.com/codeforequity-at/jsonpath.git#b76762056427dbcd149db7211f60ee0b10ed4dce)

npm WARN testmybot-sample-watson@1.0.0 No description
npm WARN testmybot-sample-watson@1.0.0 No repository field.
/Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson/node_modules/string-kit/lib/format.js:624
base = round( n / ( 1000 ** logDiv3 ) , roundStep[ logMod ] ) ;
^
SyntaxError: Unexpected token *
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson/node_modules/string-kit/lib/string.js:61:2)

npm ERR! Darwin 16.7.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "emulator"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! testmybot-sample-watson@1.0.0 emulator: npm install botium-cli && botium-cli emulator console --convos ./spec/convo --config ./testmybot.json
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the testmybot-sample-watson@1.0.0 emulator script 'npm install botium-cli && botium-cli emulator console --convos ./spec/convo --config ./testmybot.json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the testmybot-sample-watson package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm install botium-cli && botium-cli emulator console --convos ./spec/convo --config ./testmybot.json
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs testmybot-sample-watson
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls testmybot-sample-watson
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /Users/Stephen/Desktop/Project_Data/ChatSample/testmybot-master/samples/watson/npm-debug.log

@stephenws stephenws changed the title When I ran sample watson project through npm run emulatorBrowser It gives Error Cannot find module 'clear' When I ran sample watson project through npm run emulator It gives Error SyntaxError: Unexpected token * Oct 22, 2018
@Naktibalda
Copy link
Contributor

Exponentiation operator requires node 7, https://node.green/#ES2016-features-exponentiation------operator.

This issue was fixed in 0.8.15 version of string-kit at about the same time as you posted this issue,
run npm update to get a working version.

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

No branches or pull requests

2 participants