NPM semantic version control, solution console prop being mutated: "placement" error

Preface

Sorting out this knowledge point can only be said to be a coincidence , Due to the continuous iteration of the project, the project volume is too large , Caused a memory overflow , See solution ：vue Solution of project memory overflow . Because deleted node_modules and package-lock.json After downloading the dependency again, the console gives the following warning

solve

Baidu inquired , as a result of ：

When elementUi Automatically upgrade to 2.15.6 In the above version , This error will appear on the browser console .
Now see gitlab There are also many people who encounter this problem , It's all in 2.15.8 Errors appear around the version
because elementUi Upgrade to 2.15.6 The above version was in date-picker A line of direct modification has been added to the component placement Code for

After all, the solution is simple, just don't use 2.15.6 Above version , Then open your own package.json At first glance ^2.13.0 , As a result, the console still reported an error , Later, I learned that I still need to ^ Just remove it . See the following for specific reasons npm Semantic version control of

npm Semantic version control of

Reference resources （ Plagiarism ）：http://nodejs.cn/learn/semantic-versioning-using-npm

Semantic version control

The concept of semantic versioning is simple ： All versions have 3 A digital ：x.y.z.

• The first number is the main version .
• The second number is the second version .
• The third number is the patch version .

When a new version is released , It's not just about adding numbers at will , Also follow the following rules ：

• When incompatible API When changes , Upgrade the main version .
• When adding features in a backward compatible way , Then upgrade to the next version .
• When performing backward compatible defect repair , Upgrade the patch version .

This Convention is adopted in all programming languages , Every npm Software packages must comply with this Convention , This is very important , Because the whole system depends on it .
because npm Set some rules , Can be used in package.json Select the version you want to update the package to （ When running npm update when ）.

Symbol

Details of these rules are as follows ：