vvisp console: show error logs before entering "vvisp gen-script"
jason-haechi opened this issue · 0 comments
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
When I enter the "vvisp console" command before entering the "vvisp gen-script", logs is as follows.
(node:30833) UnhandledPromiseRejectionWarning: Error: Cannot find module '/Users/jasonkim/Development/HAECHILABS/service/rock-paper-scissors-contract/contractApis/back/index.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:649:15)
at Function.Module._load (internal/modules/cjs/loader.js:575:25)
at Module.require (internal/modules/cjs/loader.js:705:19)
at require (internal/modules/cjs/helpers.js:14:16)
at setApi (/Users/jasonkim/.config/yarn/global/node_modules/@haechi-labs/vvisp/scripts/console.js:372:5)
at Command.module.exports (/Users/jasonkim/.config/yarn/global/node_modules/@haechi-labs/vvisp/scripts/console.js:40:14)
at Command.listener (/Users/jasonkim/.config/yarn/global/node_modules/commander/index.js:315:8)
at Command.emit (events.js:197:13)
at Command.parseArgs (/Users/jasonkim/.config/yarn/global/node_modules/commander/index.js:654:12)
at Command.parse (/Users/jasonkim/.config/yarn/global/node_modules/commander/index.js:474:21)
at Object. (/Users/jasonkim/.config/yarn/global/node_modules/@haechi-labs/vvisp/bin/vvisp.js:6:13)
at Module._compile (internal/modules/cjs/loader.js:799:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
at Module.load (internal/modules/cjs/loader.js:666:32)
at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
at Function.Module._load (internal/modules/cjs/loader.js:598:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:862:12)
at internal/main/run_main_module.js:21:11
(node:30833) 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:30833) [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
It would be nice to show what command you need to run rather than show the error log.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
vvisp version: 1.0.2
Environment:
- Node version: 11.12.0
- Operating system: mac OS mojave 10.14.1
Others: