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

[Deprecation] Unhandled promise error #22201

Closed
joshuaSmith2021 opened this issue Aug 8, 2018 · 2 comments
Closed

[Deprecation] Unhandled promise error #22201

joshuaSmith2021 opened this issue Aug 8, 2018 · 2 comments
Labels
wrong repo Issues that should be opened in another repository.

Comments

@joshuaSmith2021
Copy link

I'm using firebase-tools, and I run firebase login, which throws this error:

(node:10422) UnhandledPromiseRejectionWarning: Error: Exited with code 3
    at ChildProcess.cp.once.code (/home/pi/.nvm/versions/node/v10.8.0/lib/node_modules/firebase-tools/node_modules/opn/index.js:84:13)
    at Object.onceWrapper (events.js:273:13)
    at ChildProcess.emit (events.js:182:13)
    at ChildProcess.EventEmitter.emit (domain.js:442:20)
    at maybeClose (internal/child_process.js:962:16)
    at Socket.stream.socket.on (internal/child_process.js:381:11)
    at Socket.emit (events.js:182:13)
    at Socket.EventEmitter.emit (domain.js:442:20)
    at Pipe._handle.close (net.js:599:12)
(node:10422) 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:10422) [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.
@mscdex
Copy link
Contributor

mscdex commented Aug 8, 2018

This issue tracker is for reporting bugs in node core and submitting feature requests for node core.

General help questions should be posted to the nodejs/help issue tracker instead.

Issues with third-party modules (e.g. firebase-tools), npm, or other tools that use node, should be posted to the appropriate issue tracker for that project, unless it can be proven that the issue is in fact with node core and not the module/tool in question.

@mscdex mscdex closed this as completed Aug 8, 2018
@mscdex mscdex added the wrong repo Issues that should be opened in another repository. label Aug 8, 2018
@joshuaSmith2021
Copy link
Author

Ok! Thanks for pointing me in a better direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

2 participants