Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] Man pages in sections 5 and 7 don’t have “npm-” prefix since 6.13.0 #780

Open
jirutka opened this issue Feb 7, 2020 · 3 comments
Open

[BUG] Man pages in sections 5 and 7 don’t have “npm-” prefix since 6.13.0 #780

jirutka opened this issue Feb 7, 2020 · 3 comments
Labels
Enhancement new feature or improvement Priority 2 secondary priority issue Release 8.x work is associated with a specific npm 8 release

Comments

@jirutka
Copy link

jirutka commented Feb 7, 2020

Since npm 6.13.0, man pages installed in man5 (from docs/content/configuring-npm/) and man7 (from docs/content/using-npm) don’t have npm- prefix. Since they use quite common names such as config or install, there’s a very high chance of collision with some other software installed on the system. Thus it’s unacceptable for Linux distributions.

Please return the npm- prefix to names of the relevant man pages as it was before version 6.13.0.
@jirutka jirutka changed the title [BUG] Man pages in sections 5 and 7 Feb 7, 2020
@jirutka jirutka changed the title [BUG] Man pages in sections 5 and 7 don’t have npm- prefix Feb 7, 2020
@darcyclarke darcyclarke added Release 6.x work is associated with a specific npm 6 release Bug thing that needs fixing labels Oct 30, 2020
@jirutka
Copy link
Author

jirutka commented Apr 8, 2022

@darcyclarke, why did you close this issue? It’s still not fixed.
@ckirbybigdog

This comment was marked as spam.

Sign in to view
@lukekarrys lukekarrys mentioned this issue Apr 10, 2022
Open
@lukekarrys lukekarrys added Release 8.x work is associated with a specific npm 8 release Enhancement new feature or improvement Priority 2 secondary priority issue and removed Release 6.x work is associated with a specific npm 6 release Bug thing that needs fixing labels Apr 10, 2022
@lukekarrys lukekarrys reopened this Apr 10, 2022
@lukekarrys
Copy link
Contributor

Reopening as I've confirmed this is still the current behavior.
theamericanaccount pushed a commit to themartiancompany/npm-ur that referenced this issue Jan 28, 2024
@polyzen
upgpkg: 8.19.2-3: Workaround npm/cli#780
2a94e7c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement new feature or improvement Priority 2 secondary priority issue Release 8.x work is associated with a specific npm 8 release
5 participants
@darcyclarke @lukekarrys @jirutka @ckirbybigdog and others