From 505f077052977c457220e2a5cbb6ec661bd3ee3c Mon Sep 17 00:00:00 2001 From: Konstantinos Lyrakis Date: Thu, 6 Dec 2018 03:20:07 +0100 Subject: [PATCH] Minor grammatical error (#34565) --- ...-npm-dependencies-by-understanding-semantic-versioning.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/curriculum/challenges/english/05-apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning.en.md b/curriculum/challenges/english/05-apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning.en.md index 4b40bdcea5..c32d422fed 100644 --- a/curriculum/challenges/english/05-apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning.en.md +++ b/curriculum/challenges/english/05-apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning.en.md @@ -9,7 +9,7 @@ challengeType: 2 Versions of the npm packages in the dependencies-section of your package.json follow what’s called Semantic Versioning (SemVer), an industry standard for software versioning aiming to make it easier to manage dependencies. Libraries, frameworks or other tools published on npm should use SemVer in order to clearly communicate what kind of changes that projects who depend on the package can expect if they update. SemVer doesn’t make sense in projects without public APIs - so unless your project is similar to the examples above, use another versioning format. So why do you need to understand SemVer? -Knowing SemVer can be useful when you develop software that use external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things “that worked yesterday” suddenly doesn’t. +Knowing SemVer can be useful when you develop software that use external dependencies (which you almost always do). One day, your understanding of these numbers will save you from accidentally introducing breaking changes to your project without understanding why things “that worked yesterday” suddenly don’t. This is how Semantic Versioning works according to the official website: Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes,