doc: add preferDev and update preferGlobal by larsgw · Pull Request #143 · npm/cli

larsgw · 2019-01-19T15:52:32Z

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw · 2019-01-19T15:52:32Z

See https://npm.community/t/4769

ljharb · 2019-01-19T16:45:26Z

 ## preferGlobal

-**DEPRECATED**
+Inform that this package is usually installed globally.


Why would this no longer be deprecated? I can’t think of any reason that a package should decide that it’s preferred globally; that always depends on the installer’s use case.

If we're having preferDev as guidance towards devDependencies, I though it might be weird if preferGlobal had the same effect but was considered deprecated. I realise installing globally isn't a meaningful distinction given npx and npm run-script, but I meant it more like a property saying "this is a CLI".

I think preferDev makes perfect sense (and preferPeer, tbh) because the action they recommend is a best practice for that package. preferGlobal is, at best, recommending a bad practice that’s blessed by that package’s authors.

darcyclarke · 2020-02-18T17:22:22Z

Unfortunately preferDev isn't implemented today. Updating the docs would be inaccurate. Definitely feel free to create an RFC for this.

larsgw requested a review from a team as a code owner January 19, 2019 15:52

ljharb reviewed Jan 19, 2019
View reviewed changes

zkat force-pushed the release-next branch from 62154bf to 82170b4Compare January 22, 2019 21:21

aeschright added the docs label Jan 22, 2019

zkat force-pushed the release-next branch 2 times, most recently from db63b89 to b09bc8cCompare January 23, 2019 18:36

zkat added the needs-discussion label Jan 28, 2019

larsgw force-pushed the patch-18 branch from 931eaeb to 71659eeCompare January 29, 2019 18:58

zkat force-pushed the release-next branch 2 times, most recently from 06cdf5b to f957798Compare February 20, 2019 20:42

doc: add preferDev and update preferGlobal
829cedf

larsgw force-pushed the patch-18 branch from 71659ee to 829cedfCompare February 21, 2019 23:27

doc: re-deprecate preferGlobal
6f69cde

isaacs force-pushed the release-next branch 2 times, most recently from 896149d to 31718e7Compare June 29, 2019 21:55

settingsBot removed docs labels Nov 5, 2019

This was referenced Feb 1, 2020
[Snyk] Fix for 1 vulnerabilities Bhanditz/cli#3
Open
[Snyk] Fix for 1 vulnerabilities bumplzz69/cli#2
Open
[Snyk] Fix for 1 vulnerabilities dongseok1985/cli#3
Open

darcyclarke closed this Feb 18, 2020

This was referenced Sep 15, 2021
[Snyk] Fix for 1 vulnerabilities Bhanditz/cli#20
Open
[Snyk] Fix for 1 vulnerabilities Jankyboy/cli-1#35
Open
[Snyk] Fix for 1 vulnerabilities mtdev2/cli#77
Open
[Snyk] Fix for 1 vulnerabilities thebpc/cli#31
Open

This was referenced Sep 28, 2021
[Snyk] Security upgrade update-notifier from 2.5.0 to 3.0.0 Jankyboy/cli-1#39
Open
[Snyk] Security upgrade update-notifier from 2.5.0 to 3.0.0 dongseok1985/cli#19
Open
[Snyk] Security upgrade update-notifier from 2.5.0 to 3.0.0 Bhanditz/cli#22
Open

kevinjm39 mentioned this pull request May 1, 2022
[Snyk] Upgrade pacote from 13.0.3 to 13.1.1 kevinjm39/cli#2
Open

kevinjm39 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities kevinjm39/cli#16
Open

CALISOULB mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#19
Open

varmakarthik12 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#30
Closed

bumplzz69 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities bumplzz69/cli#38
Open

mtdev2 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities mtdev2/cli#91
Open

Bhanditz mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities Bhanditz/cli#29
Open

baby636 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities baby636/cli#62
Open

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 7, 2026
📊 대시보드 데이터 업데이트 (npm#143)
f225fa0

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 19, 2026
🔧 자동 수리 완료 (npm#143)
6bbe5e0

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 11, 2026
🔥 트렌드 선점 후보 갱신 (npm#143)
893da8a