pkgmgr 1.1.0 → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
A minimal CLI that forwards commands to whichever package manager you're already using.
|
|
4
4
|
|
|
5
|
+
<a href="https://github.com/epicweb-dev/full-stack-foundations/commit/fdb0644909a6d5e847b9bf3fb12e8efd120aa036">
|
|
6
|
+
<img src="./demo.png" alt="Diff showing package.json scripts being updated to use pkgmgr instead of npm. Scripts like postinstall, start, dev, build, and test are changed from using npm and npx to pkgmgr and pkgmgrx. The result: these scripts now work seamlessly whether contributors use npm, pnpm, yarn, or bun." style="max-width: 691px; max-height: 868px;" />
|
|
7
|
+
</a>
|
|
8
|
+
|
|
9
|
+
**What's happening here:** A project replaces hardcoded `npm` and `npx` calls with `pkgmgr` and `pkgmgrx` in their package.json scripts. Now when a contributor runs `pnpm run dev`, the script uses `pnpm`. When another runs `bun run dev`, it uses `bun`. No configuration, no conditional logic—just automatic package manager detection.
|
|
10
|
+
|
|
5
11
|
## The Problem
|
|
6
12
|
|
|
7
13
|
You're writing a script, a tool, or documentation that needs to run package manager commands. But different users use different package managers (npm, pnpm, yarn, bun), and you don't want to:
|