What is the version number of package.json?
This article is to share with you what the package.json version number is, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.
I. brief introduction of version number
The software version number consists of four parts:
The first part is the main version number, which indicates that there is a big change that is not compatible with the previous version.
The second part is the minor version number, which means that new features have been added and can be backwards compatible.
The third part is the revision number, which means that there is a bug fix and is backward compatible.
The fourth part is the date version number plus the Greek alphabet version number. There are five Greek alphabet version numbers, namely base, alpha, beta, RC and release.
Eg:
About the Greek version number:
Base
This version indicates that the software is only a fake page link, usually including all the functions and page layout, but the functions in the page are not fully implemented, just as an infrastructure of the overall site.
Alpha
The initial version of the software indicates that the main purpose of the software at this stage is to realize the software function, and it is usually only communicated among the software developers. Generally speaking, this version of the software has more Bug and needs to be modified, so it is the test version. After the tester submits the Bug to be modified and confirmed by the developer, it is posted to the test URL for the tester to test. At this time, the software version can be marked as alpha version.
Beta
Compared with the Alpha version, this version has made great progress and eliminated serious errors, but it still needs to be further eliminated after many tests. the main modification object of this version is the software UI. The modified Bug can be released to the public network after being tested and confirmed by the tester, and the software version can be marked as beta version at this time.
RC
This version is so mature that there is basically no Bug that caused the error, much the same as the upcoming official version.
Release
This version means the "final version", and after a series of beta versions of the previous version, there will eventually be a formal version, which is the final version delivered to the user. This version is sometimes called the standard version.
2. Dependency in package.json
The dependencies field specifies the modules on which the project runs, and the devDependencies specifies the modules required for project development (the dependencies of the test phase and transition phase should be added to the DevDependencies). They all point to the same object. Each member of the object consists of the module name and the corresponding version requirements, indicating the dependent module and its version scope.
Eg:
{
"name": "ethopia-waza"
"description": "a delightfully fruity coffee varietal"
"version": "1.2.3"
"devDependencies": {
"coffee-script": "~ 1.6.3"
}
"dependencies": {
"bar": "file:../foo/bar"
}
}
The module name and version number are assumed to be combined into a unique identifier.
The version field must be parsed by node-semver. Node-semver is bundled into npm as a dependency.
In fact, the version number is not only the well-known tilde (~ 3.8.0), caret (^ 3.8.0) and 3.8.0, as long as it can be parsed by node-semver.
There are mainly the following:
Example:
Version must exactly match this version
> version must be greater than this version
> = version must be greater than or equal to this version
< version must be less than this version
= version1 = 2.3.1 = 2.3.1 < 3.0.0, do not change the large version number.
"qux": "= 2.3.1 = 2.5.2
