vvisp console: babel parse error

[nujabes403]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

Current behavior

After vvisp init && vvisp compile && vvisp deploy-contract command, vvisp console throws following error:

❯ vvisp console
(node:34399) UnhandledPromiseRejectionWarning: SyntaxError: /Users/hoonilkim/work2/myDapp2/contractApis/back/index.js: Unexpected token (9:4)
   7 |   return {
   8 |     config: setters.config,
>  9 |     ...loadApis()
     |     ^
  10 |   };
  11 | };
  12 | 
    at Parser.pp$5.raise (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:4454:13)
    at Parser.pp.unexpected (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:1761:8)
    at Parser.pp$3.parseIdentifier (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:4332:10)
    at Parser.pp$3.parsePropertyName (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:4156:96)
    at Parser.pp$3.parseObj (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:4045:12)
    at Parser.pp$3.parseExprAtom (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3719:19)
    at Parser.pp$3.parseExprSubscripts (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3494:19)
    at Parser.pp$3.parseMaybeUnary (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3474:19)
    at Parser.pp$3.parseExprOps (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3404:19)
    at Parser.pp$3.parseMaybeConditional (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3381:19)
    at Parser.pp$3.parseMaybeAssign (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3344:19)
    at Parser.pp$3.parseExpression (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3306:19)
    at Parser.pp$1.parseReturnStatement (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:2078:26)
    at Parser.pp$1.parseStatement (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:1848:19)
    at Parser.pp$1.parseBlockBody (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:2268:21)
    at Parser.pp$1.parseBlock (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:2247:8)
    at Parser.pp$3.parseFunctionBody (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:4235:22)
    at Parser.pp$1.parseFunction (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:2386:8)
    at Parser.pp$3.parseFunctionExpression (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3760:17)
    at Parser.pp$3.parseExprAtom (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3722:19)
    at Parser.pp$3.parseExprSubscripts (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3494:19)
    at Parser.pp$3.parseMaybeUnary (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3474:19)
    at Parser.pp$3.parseExprOps (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3404:19)
    at Parser.pp$3.parseMaybeConditional (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3381:19)
    at Parser.pp$3.parseMaybeAssign (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3344:19)
    at Parser.pp$3.parseMaybeAssign (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3367:23)
    at Parser.pp$3.parseExpression (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:3306:19)
    at Parser.pp$1.parseStatement (/Users/hoonilkim/work2/myDapp2/node_modules/babylon/lib/index.js:1906:19)
(node:34399) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:34399) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected behavior

vvisp console should not throw an babel parsing error.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

vvisp version: X.Y.Z


Environment:
- Node version:
- Operating system:

Others: