Skip to content
This repository has been archived by the owner on Sep 20, 2021. It is now read-only.

grunt serve causes UnhandledPromiseRejectionWarning #123

Open
davewood opened this issue Apr 8, 2020 · 1 comment
Open

grunt serve causes UnhandledPromiseRejectionWarning #123

davewood opened this issue Apr 8, 2020 · 1 comment

Comments

@davewood
Copy link
Contributor

davewood commented Apr 8, 2020

Running "watch" task
Waiting...
(node:124) UnhandledPromiseRejectionWarning: Error: Exited with code 3
    at ChildProcess.<anonymous> (/home/cert/customer-portal/node_modules/opn/index.js:85:13)
    at Object.onceWrapper (events.js:422:26)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1026:16)
    at Socket.<anonymous> (internal/child_process.js:441:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:674:12)

(node:124) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:124) [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.

bpmn-io/bpmn-js-examples#34
https://stackoverflow.com/questions/34596085/grunt-watch-fails-with-message-running-watch-task-waiting-warning-maximu

@davewood
Copy link
Contributor Author

caused by 3rd party module "opn". waiting for frontend rework.

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

No branches or pull requests

1 participant