If module Z decided to release a new version 1.3.0, then when you run NPM install, it will automatically upgrade it to 1.3.0 since you specify it as ^(caret) in package.json. Suppose you have a dependency with module ~1.0.1, and module X depends on module ^1.1.0 and module Y depends on module ^1.2.0 Even a month old library example code often becomes broken and you need to search for change logs to figure out what’s changed. It’s not about documentation and testing I am talking about well that’s a completely different story. Libraries are changing and growing really fast, they rarely do versioning right. This is a common problem within the NPM ecosystem which every developer faces. The answer is bad dependency tree management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |