From 1b0518202a573f3396a19b44db02d2b4a0a32e4e Mon Sep 17 00:00:00 2001 From: Jose Toledo Date: Tue, 15 Jan 2019 13:59:18 -0800 Subject: [PATCH] Added a dependency convention code example (#25515) --- .../index.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md b/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md index 8d46a6ca3f..7d3e4e5fe7 100644 --- a/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md +++ b/guide/english/certifications/apis-and-microservices/managing-packages-with-npm/manage-npm-dependencies-by-understanding-semantic-versioning/index.md @@ -3,8 +3,14 @@ title: Manage npm Dependencies By Understanding Semantic Versioning --- ## Manage npm Dependencies By Understanding Semantic Versioning -This is a stub. Help our community expand it. - -This quick style guide will help ensure your pull request gets accepted. - +You should go over to the `package.json` file in your project. SemVer dependencies follow a similar convention like this: + +```code +"dependencies": { + "dependency1": "^major.minor.patch" + }, + ... +``` + +This is a stub. Help our community expand it.