This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 45
node-report: sunsetting the module, archiving the repo #142
Comments
I don't believe diagnostic report has been or will be backported to Node.js 10 so we shouldn't archive this repository until Node.js 10 goes End-of-Life. |
Merged
richardlau
pushed a commit
that referenced
this issue
Apr 15, 2020
PR-URL: #144 Refs: #142 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
4 tasks
Node.js 10 is now End-of-Life and all currently supported versions of Node.js (i.e. 12, 14 and 16) contain the built in diagnostics report feature. So I propose:
I'll wait until the end of this week in case there are any objections/comments on the deprecation wording. |
Module is now deprecated in the registry:
|
Opened nodejs/admin#621 to request that this repository be archived. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
diagnostic report is now stable in the master: nodejs/node#32242 , hopefully will make it into node.js v14 next month. The only known bug is being worked out too.
This issue is to identify and discuss any other pre-requisites or conditions that need to be met for this repo to be archived and the
npm
module to be sunset, derive at a consensus.The text was updated successfully, but these errors were encountered: