enhanced-publish 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 +2 -2
package/README.md
CHANGED
|
@@ -10,6 +10,12 @@
|
|
|
10
10
|
The package is a command line tool that can be used to publish your package to npm.
|
|
11
11
|
It works exactly like [npm publish](https://docs.npmjs.com/cli/v8/commands/npm-publish) but it also allows you to specify to only publish the package if there is no version conflict.
|
|
12
12
|
|
|
13
|
+
### --if-possible
|
|
14
|
+
|
|
13
15
|
The behavior is heavily inspired by lerna's [from-package](https://github.com/lerna/lerna/tree/main/commands/publish#bump-from-package) publishing strategy.
|
|
14
16
|
|
|
15
17
|
The command adds a flag `--if-possible` to the `npm publish` command and will not publish if the package already exists in the registry.
|
|
18
|
+
|
|
19
|
+
### --use-preid-as-tag
|
|
20
|
+
|
|
21
|
+
Will use the '[preid](https://docs.npmjs.com/cli/v8/commands/npm-version#preid)' as the tag. `1.0.0-alpha.1` becomes `--tag alpha` in the publish command.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "enhanced-publish",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.1",
|
|
4
4
|
"description": "Npm publish command with lerna's from-package publish behaviour.",
|
|
5
5
|
"repository": "github:js-soft/enhanced-npm-publish",
|
|
6
6
|
"license": "MIT",
|
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
"index.js"
|
|
11
11
|
],
|
|
12
12
|
"dependencies": {
|
|
13
|
-
"pacote": "^
|
|
13
|
+
"pacote": "^15.0.6"
|
|
14
14
|
},
|
|
15
15
|
"publishConfig": {
|
|
16
16
|
"access": "public"
|