-
Notifications
You must be signed in to change notification settings - Fork 274
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
Remove dependency on Q
in favor of native Promises
#900
Comments
Hi @JamieMagee, thanks for reporting this. |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
This issue isn't stale |
This would be great, Jamie has also kindly opened a pull request for this too! #905 |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
Still would be nice |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
This is not totally complete. As of the pull of #905 "This only handles the node directory. There are still uses of Q under the powershell directory.", so this issue is not resolved. |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
Not stale |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
This isn't completed. Please re-open the issue. Thanks. |
Environment
azure-pipelines-task-lib version: 3.4.0
Issue Description
azure-pipelines-task-lib
currently has a hard dependency onq
, a Promise library for JavaScript. This was necessary in the early days of JavaScript, but since ES6/ES2015 the JavaScript standard has had native support for Promises.q
hasn't published a new release in over 5 years, and has a note on the GitHub repoSupport for native Promises in Node has been available since Node v4.
Expected behaviour
No dependency on
q
Actual behaviour
A dependency on
q
The text was updated successfully, but these errors were encountered: