-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
handling unhandledRejection for support of nodejs version < 15.x.x
#234
Comments
NOTE: |
>=15
<15
<15
< 15
< 15
15.x.x
@magicmatatjahu is the issue still up for work? If so I would like to work on this. :) |
@magicmatatjahu ,just curious, how do we start working on this now as watcher is ready :) |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
This is already solved ..mr bot 🤭 |
With introduction to NodeJS 15 blog
https://developer.ibm.com/blogs/nodejs-15-release-blog/
All unhandled rejections will be treated as strictly as errors , instead of warnings. Hence the process will be closed.
This is directly affecting our cli watcher for nodejs < 15 and nodejs > 15, as mentioned here #220 (comment)
@magicmatatjahu has suggested the following solution to this
This issue tries to address the above problem
The text was updated successfully, but these errors were encountered: