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
Click "To report bugs or submit feature requests for the docs, please post here."
Expected Behavior
There should be a banner or other indication that the site is inactive/deprecated/read only and to point people towards the correct place to register issues.
npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.
If your bug is reproducible on v7, please re-file this issue using our new issue template.
If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo
What / Why
There is no indication that the npm.community website is inactive/deprecated and read only.
When
When you arrive at npm.community (e.g. https://npm.community/c/support/docs-needed) as sent to from (https://docs.npmjs.com/).
Where
npm.community
How
Current Behavior
The npm.community site appears to be active and the correct place for creating and tracking npm issues.
Steps to Reproduce
Expected Behavior
There should be a banner or other indication that the site is inactive/deprecated/read only and to point people towards the correct place to register issues.
Who
Not sure?
References
The text was updated successfully, but these errors were encountered: