oclif 4.3.10 → 4.4.0
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/lib/commands/lock.js +8 -1
- package/oclif.manifest.json +7 -2
- package/package.json +1 -1
package/lib/commands/lock.js
CHANGED
|
@@ -22,9 +22,16 @@ class Lock extends core_1.Command {
|
|
|
22
22
|
}
|
|
23
23
|
}
|
|
24
24
|
static {
|
|
25
|
+
this.hidden = true;
|
|
26
|
+
this.state = 'deprecated';
|
|
25
27
|
this.summary = 'Copy the yarn.lock to oclif.lock';
|
|
28
|
+
this.deprecationOptions = {
|
|
29
|
+
message: 'oclif.lock is deprecated and will be removed in @oclif/plugin-plugins v5.0.0 and above.',
|
|
30
|
+
};
|
|
26
31
|
this.description = `Using oclif.lock allows your plugins dependencies to be locked to the version specified in the lock file during plugin install.
|
|
27
|
-
Once the oclif.lock file is created you can include it your npm package by adding it to the files property of your package.json. We do not recommend committing the oclif.lock file to git
|
|
32
|
+
Once the oclif.lock file is created you can include it your npm package by adding it to the files property of your package.json. We do not recommend committing the oclif.lock file to git.
|
|
33
|
+
|
|
34
|
+
PLEASE NOTE: the oclif.lock will only work for @oclif/plugin-plugins v3.4.0 and above. It will NOT be supported in v5.0.0 and above.`;
|
|
28
35
|
}
|
|
29
36
|
}
|
|
30
37
|
exports.default = Lock;
|
package/oclif.manifest.json
CHANGED
|
@@ -35,14 +35,19 @@
|
|
|
35
35
|
"lock": {
|
|
36
36
|
"aliases": [],
|
|
37
37
|
"args": {},
|
|
38
|
-
"
|
|
38
|
+
"deprecationOptions": {
|
|
39
|
+
"message": "oclif.lock is deprecated and will be removed in @oclif/plugin-plugins v5.0.0 and above."
|
|
40
|
+
},
|
|
41
|
+
"description": "Using oclif.lock allows your plugins dependencies to be locked to the version specified in the lock file during plugin install.\nOnce the oclif.lock file is created you can include it your npm package by adding it to the files property of your package.json. We do not recommend committing the oclif.lock file to git.\n\nPLEASE NOTE: the oclif.lock will only work for @oclif/plugin-plugins v3.4.0 and above. It will NOT be supported in v5.0.0 and above.",
|
|
39
42
|
"flags": {},
|
|
40
43
|
"hasDynamicHelp": false,
|
|
44
|
+
"hidden": true,
|
|
41
45
|
"hiddenAliases": [],
|
|
42
46
|
"id": "lock",
|
|
43
47
|
"pluginAlias": "oclif",
|
|
44
48
|
"pluginName": "oclif",
|
|
45
49
|
"pluginType": "core",
|
|
50
|
+
"state": "deprecated",
|
|
46
51
|
"strict": true,
|
|
47
52
|
"summary": "Copy the yarn.lock to oclif.lock",
|
|
48
53
|
"enableJsonFlag": false,
|
|
@@ -732,5 +737,5 @@
|
|
|
732
737
|
]
|
|
733
738
|
}
|
|
734
739
|
},
|
|
735
|
-
"version": "4.
|
|
740
|
+
"version": "4.4.0"
|
|
736
741
|
}
|