@orangemug/oops 0.2.2 → 0.2.4
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 +8 -2
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,6 +1,12 @@
|
|
|
1
1
|
# `@orangemug/oops`
|
|
2
2
|
|
|
3
|
-
Have I got a
|
|
3
|
+
Have I got a pacakge version in my npm/pnpm/yarn cache?
|
|
4
|
+
|
|
5
|
+
## Why?
|
|
6
|
+
|
|
7
|
+
I kept having to look up the CLI commands to check every time there was a npm package compromise, across the various package managers npm/pnpm/yarn.
|
|
8
|
+
|
|
9
|
+
This does that for me in one-shot and something I can share.
|
|
4
10
|
|
|
5
11
|
## Usage
|
|
6
12
|
|
|
@@ -9,7 +15,7 @@ Find out with `oops`
|
|
|
9
15
|
```bash
|
|
10
16
|
npx @orangemug/oops --help
|
|
11
17
|
# npx @orangemug/oops <dangerous_package_versions>
|
|
12
|
-
#
|
|
18
|
+
#
|
|
13
19
|
# Example: npx @orangemug/oops '@ctrl/tinycolor:4.1.1' '@ctrl/tinycolor:4.1.2'
|
|
14
20
|
```
|
|
15
21
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@orangemug/oops",
|
|
3
|
-
"description": "Have I got a
|
|
4
|
-
"version": "0.2.
|
|
3
|
+
"description": "Have I got a package version in my cache?",
|
|
4
|
+
"version": "0.2.4",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
7
7
|
"url": "https://github.com/orangemug/oops"
|