blocks|key|449717|text|这是我通常对我的项目所做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449718|npm+version+patch
git+add+*;
git+commit+-m+"Commit+message"
git+push
npm+publish|code-block|syntax|javascript|449719|第一行npm+version+patch将把package.json中的补丁版本增加1+(x.x.1到x.x.2)。然后添加所有文件--包括当时已经修改过的package.json。然后，通常使用git+commit和git+push，最后使用npm+publish发布模块。|offset|length|style|CODE|449720|我希望这是有意义的。|449721|默克。|449722|entityMap^0|0|0|3|H|M|C|26|C|2Q|A|31|8|3E|B|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$]]

This is what I normally do with my projects:

<pre><code>npm version patch
git add *;
git commit -m "Commit message"
git push
npm publish
</code></pre>

The first line, <code>npm version patch</code>, will increase the patch version by 1 (x.x.1 to x.x.2) in <code>package.json</code>. Then you add all files -- including <code>package.json</code> which at that point has been modified.
Then, the usual <code>git commit</code> and <code>git push</code>, and finally <code>npm publish</code> to publish the module.

I hope this makes sense...

Merc.

blocks|key|449737|text|npm+version可能是正确的答案。为了给出另一种选择，我推荐grunt-bump。它是由angular.js的一个人维护的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|449738|用法：|449739|grunt+bump
>>+Version+bumped+to+0.0.2

grunt+bump:patch
>>+Version+bumped+to+0.0.3

grunt+bump:minor
>>+Version+bumped+to+0.1.0

grunt+bump
>>+Version+bumped+to+0.1.1

grunt+bump:major
>>+Version+bumped+to+1.0.0|code-block|syntax|javascript|449740|如果你正在使用grunt，这可能是最简单的解决方案。|449741|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/vojtajina/grunt-bump^0|0|B|X|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|14|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

<code>npm version</code> is probably the correct answer. Just to give an alternative I recommend <a href="https://github.com/vojtajina/grunt-bump">grunt-bump</a>. It is maintained by one of the guys from angular.js.

Usage:

<pre><code>grunt bump
&gt;&gt; Version bumped to 0.0.2

grunt bump:patch
&gt;&gt; Version bumped to 0.0.3

grunt bump:minor
&gt;&gt; Version bumped to 0.1.0

grunt bump
&gt;&gt; Version bumped to 0.1.1

grunt bump:major
&gt;&gt; Version bumped to 1.0.0
</code></pre>

If you're using grunt anyway it might be the simplest solution.

blocks|key|231868|text|作为对npm+version的补充，如果您想要一个版本提升但没有标记或新的提交，您可以使用--no-git-tag-version标志：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|231869|npm+--no-git-tag-version+version+patch|code-block|syntax|javascript|231870|https://docs.npmjs.com/cli/version|231871|entityMap|0|LINK|mutability|MUTABLE|url^0|3|B|19|K|0|0|0|Y|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|M|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|L]]]]

As an addition to <code>npm version</code> you can use the <code>--no-git-tag-version</code> flag if you want a version bump but no tag or a new commit:

<pre><code>npm --no-git-tag-version version patch
</code></pre>

<a href="https://docs.npmjs.com/cli/version" rel="noreferrer">https://docs.npmjs.com/cli/version</a>

blocks|key|449815|text|如果你使用的是纱线，你可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449816|yarn+version+--patch|code-block|syntax|javascript|449817|这将通过修补(0.0.x)、提交并使用v0.0.0格式对其进行标记来增加package.json版本|offset|length|style|CODE|449818|同样，您可以使用--minor或--major来提升次要版本或主要版本|449819|在推送到git时，请确保也使用--follow-tags推送标签|449820|git+push+--follow-tags|449821|您还可以为其创建脚本|449822|++++"release-it":+"yarn+version+--patch+&&+git+push+--follow-tags"|449823|只需输入yarn+release-it即可运行它|449824|entityMap^0|0|0|6|7|J|6|10|C|0|8|7|G|7|0|F|D|0|0|0|0|4|F|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@$I|13|J|14|K|L]|$I|15|J|16|K|L]|$I|17|J|18|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@$I|1A|J|1B|K|L]|$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1E|8|@$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1K|8|@$I|1L|J|1M|K|L]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|Z|$]]

If you are using yarn you can use 

<pre><code>yarn version --patch
</code></pre>

This will increment <code>package.json</code> version by patch <code>(0.0.x)</code>, commit, and tag it with format <code>v0.0.0</code>

Likewise you can bump minor or major version by using <code>--minor</code> or <code>--major</code>

When pushing to git ensure you also push the tags with <code>--follow-tags</code>

<pre><code>git push --follow-tags
</code></pre>

You can also create a script for it

<pre><code> "release-it": "yarn version --patch &amp;&amp; git push --follow-tags"
</code></pre>

Simply run it by typing <code>yarn release-it</code>

blocks|key|231939|text|我已经创建了一个tool，它可以基于提交消息中的标签完成自动语义版本控制，称为更改类型。这严格遵循Angular+Commit消息约定以及语义版本规范。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|231940|您可以使用此工具通过npm+CLI+(描述为here)自动更改package.json中的版本。|231941|此外，它还可以从这些提交创建changelog，并且还具有一个菜单(带有用于提交消息的拼写检查器)，用于根据更改类型创建提交。我强烈建议查看它并阅读文档，以了解使用它可以完成的一切。|231942|我之所以写这个工具，是因为我找不到任何适合我的CICD+Pipeline自动化语义版本控制需求的工具。我更愿意关注实际的变化，而不是版本应该是什么，这就是我的工具节省时间的地方。|231943|有关该工具的基本原理的更多信息，请访问see+this。|231944|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/GetchaDEAGLE/eagle-versioner|1|https://github.com/GetchaDEAGLE/eagle-versioner#versioning-automation|2|https://danieleagle.com/2020/01/introducing-eagle-versioner/^0|8|4|0|0|M|4|1|0|0|0|J|8|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]|V|$5|O|P|Q|C|$R|W]]]]

I have created a <a href="https://github.com/GetchaDEAGLE/eagle-versioner" rel="nofollow noreferrer">tool</a> that can accomplish automatic semantic versioning based on the tags in commit messages, known as change types. This closely follows the Angular Commit Message Convention along with the Semantic Versioning Specification.

You could use this tool to automatically change the version in the package.json using the npm CLI (this is described <a href="https://github.com/GetchaDEAGLE/eagle-versioner#versioning-automation" rel="nofollow noreferrer">here</a>). 

In addition, it can create a changelog from these commits and also has a menu (with a spell checker for commit messages) for creating commits based on the change type. I highly recommend checking it out and reading to docs to see everything that can be accomplished with it.

I wrote the tool because I couldn't find anything that suited my needs for my CICD Pipeline to automate semantic versioning. I'd rather focus on what the actual changes are than what the version should be and that's where my tool saves the day.

For more information on the rationale for the tool, please <a href="https://danieleagle.com/2020/01/introducing-eagle-versioner/" rel="nofollow noreferrer">see this</a>.

blocks|key|231983|text|如果您想要使用npm包semver+link来执行此操作，请注意。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|231984|let+fs+=+require('fs');
let+semver+=+require('semver');

if+(fs.existsSync('./package.json'))+{
++++var+package+=+require('./package.json');
++++let+currentVersion+=+package.version;
++++let+type+=+process.argv[2];
++++if+(!['major',+'minor',+'patch'].includes(type))+{
++++++++type+=+'patch';
++++}

++++let+newVersion+=+semver.inc(package.version,+type);
++++package.version+=+newVersion;
++++fs.writeFileSync('./package.json',+JSON.stringify(package,+null,+2));

++++console.log('Version+updated',+currentVersion,+'=>',+newVersion);
}|code-block|syntax|javascript|231985|package.json应该是这样的，|231986|{
++"name":+"versioning",
++"version":+"0.0.0",
++"description":+"Update+version+in+package.json+using+npm+script",
++"main":+"version.js",
++"scripts":+{
++++"test":+"echo+\"Error:+no+test+specified\"+&&+exit+1",
++++"version":+"node+version.js"
++},
++"author":+"Bhadresh+Arya",
++"license":+"ISC",
++"dependencies":+{
++++"semver":+"%5E7.3.2"
++}
}|231987|只需向npm+run+version传递major、minor、patch参数即可。默认值为patch。|231988|示例：npm+run+version、npm+run+verison+patch、npm+run+verison+minor或npm+run+version+major|231989|Git+Repo|231990|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/semver|1|https://github.com/bhadresharya/stationary/tree/master/fs-semver^0|B|6|I|4|0|0|0|0|C|0|0|3|F|K|5|Q|5|W|5|1A|5|0|3|F|J|L|15|L|1R|L|0|0|8|1|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1Q|8|@$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1Z|8|@]|D|@$9|20|A|21|1|22]]|E|$]]|$1|U|3|-4|5|6|7|23|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

Just in case if you want to do this using an npm package <code>semver</code> <a href="https://www.npmjs.com/package/semver" rel="nofollow noreferrer">link</a>
<pre><code>let fs = require('fs');
let semver = require('semver');

if (fs.existsSync('./package.json')) {
 var package = require('./package.json');
 let currentVersion = package.version;
 let type = process.argv[2];
 if (!['major', 'minor', 'patch'].includes(type)) {
 type = 'patch';
 }

 let newVersion = semver.inc(package.version, type);
 package.version = newVersion;
 fs.writeFileSync('./package.json', JSON.stringify(package, null, 2));

 console.log('Version updated', currentVersion, '=&gt;', newVersion);
}
</code></pre>
<code>package.json</code> should look like,
<pre><code>{
 &quot;name&quot;: &quot;versioning&quot;,
 &quot;version&quot;: &quot;0.0.0&quot;,
 &quot;description&quot;: &quot;Update version in package.json using npm script&quot;,
 &quot;main&quot;: &quot;version.js&quot;,
 &quot;scripts&quot;: {
 &quot;test&quot;: &quot;echo \&quot;Error: no test specified\&quot; &amp;&amp; exit 1&quot;,
 &quot;version&quot;: &quot;node version.js&quot;
 },
 &quot;author&quot;: &quot;Bhadresh Arya&quot;,
 &quot;license&quot;: &quot;ISC&quot;,
 &quot;dependencies&quot;: {
 &quot;semver&quot;: &quot;^7.3.2&quot;
 }
}
</code></pre>
just pass <code>major</code>, <code>minor</code>, <code>patch</code> argument with <code>npm run version</code>. Default will be <code>patch</code>.
example:
<code>npm run version</code> or <code>npm run verison patch</code> or <code>npm run verison minor</code> or <code>npm run version major</code>
<a href="https://github.com/bhadresharya/stationary/tree/master/fs-semver" rel="nofollow noreferrer">Git Repo</a>

blocks|key|449973|text|使用Husky|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|449974|{
++"name":+"demo-project",
++"version":+"0.0.3",
++"husky":+{
++++"hooks":+{
++++++"pre-commit":+"npm+--no-git-tag-version+version+patch+&&+git+add+."
++++}
++}
}|code-block|syntax|javascript|449975|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/typicode/husky^0|2|5|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

With <a href="https://github.com/typicode/husky" rel="nofollow noreferrer">Husky</a>:
<pre class="lang-json prettyprint-override"><code>{
 &quot;name&quot;: &quot;demo-project&quot;,
 &quot;version&quot;: &quot;0.0.3&quot;,
 &quot;husky&quot;: {
 &quot;hooks&quot;: {
 &quot;pre-commit&quot;: &quot;npm --no-git-tag-version version patch &amp;&amp; git add .&quot;
 }
 }
}
</code></pre>

blocks|key|449999|text|您可以使用version-select包：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|450000|npm+i+-D+version-select|code-block|syntax|javascript|450001|{
++++"name":+"test",
++++"version":+"1.0.0",
++++"scripts":+{
++++++++"version-select":+"version-select"
++++},
++++"devDependencies":+{
++++++++"version-select":+"%5E1.0.13"
++++}
}|450002|​|450003|📷|atomic|450004|450005|Read+more|450006|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e6f7f8ca28e33083f8ae957752008c1a.gif|imageAlt|1|LINK|MUTABLE|url|https://www.npmjs.com/package/version-select^0|5|E|0|0|0|0|0|1|0|0|0|0|9|1|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|M|3|N|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|R|3|N|5|6|7|1I|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1J|8|@]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|U|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11|12|-4]]|13|$5|14|Y|15|E|$16|17]]]]

You can use the <code>version-select</code> package:
<pre class="lang-sh prettyprint-override"><code>npm i -D version-select
</code></pre>
<pre class="lang-json prettyprint-override"><code>{
 &quot;name&quot;: &quot;test&quot;,
 &quot;version&quot;: &quot;1.0.0&quot;,
 &quot;scripts&quot;: {
 &quot;version-select&quot;: &quot;version-select&quot;
 },
 &quot;devDependencies&quot;: {
 &quot;version-select&quot;: &quot;^1.0.13&quot;
 }
}

</code></pre>
<a href="https://i.stack.imgur.com/CfaLR.gif" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CfaLR.gif" alt="enter image description here" /></a>
<a href="https://www.npmjs.com/package/version-select" rel="nofollow noreferrer">Read more</a>

Before I do a small release and tag it, I'd like to update the package.json to reflect the new version of the program.

Is there a way to edit the file <code>package.json</code> automatically?

Would using a <code>git pre-release hook</code> help?

update package.json version automatically

JSON

在我发布一个小版本并标记它之前，我想更新一下package.json以反映程序的新版本。有没有办法自动编辑package.json文件？使用git pre-release hook会有帮助吗？

问自动更新package.json版本
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问自动更新package.json版本EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问自动更新package.json版本
EN