You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 18, 2021. It is now read-only.
node-report: sunsetting the module, archiving the repo #142
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.
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.
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:
Deprecating the package on the npm registry. I propose setting a deprecation message of
This module has been superseded by the diagnostics report feature of Node.js core. It is now unmaintained.
$ npm install node-report
npm WARN deprecated node-report@2.2.11: This module has been superseded by the diagnostics report feature of Node.js core. It is now unmaintained.
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
npmmodule to be sunset, derive at a consensus.