Node JS

NPM Demystified Part-2 : Semantic Versioning Explained.

Let’s check our current package.json

"dependencies": {
"lodash": "^4.17.4"

Semantic Versioning:

In the dependencies, you can find lodash followed by version number. All the node modules follow semantic versioning.

Given a version number MAJOR.MINOR.PATCH and in our lodash example 4 is the major version, 17 is the minor version and 4 is the patch version. We should update the:
source link MAJOR version when incompatible API changes made in our module.
follow MINOR version when we add functionality with backward-compatible.
source PATCH version when you make minor bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

We also need to follow semantic versioning system for our node application. ☝☝Question: Now I’m ok with the version number, Why ^ symbol used before the version number?

Before Major version, you can able to find ^ symbol. You can use ~, ^ or * with the version details.

should i lose weight before i start dating Patch releases: 1.0 or 1.0.x or ~1.0.4 Minor releases: 1 or 1.x or ^1.0.4
femme recherche trip a 3 Major releases: * or x

Let me explain little deeper. Usually, when we push our code to the repository (Git, svn, cvs or Mercurial) we should ignore the node_modules directory because when we add multiple node modules repo will consume huge volume. So User who checks out the code will do npm install and it will install all the modules mentioned in the dependencies of package.json.

Here comes the problem, npm doesn’t know which version to install and using ~, ^ and * we can make sure npm install’s the right version of packages for us. when ~ is used it will install the latest patch version, when ^ is used it will install latest minor version and when * is used npm will install the latest version of the package. We can use ~ and ^ in our package.json because * doesn’t have backward compatibility so it will break the existing code and logic.

These symbols should be managed correctly to avoid versioning problem with the developers and it explains the importance of –save during installation.

OOPS!! Long answer for a small question!!

forex kurs usd ☝☝Question: shall I modify the version details directly in package.json?

Yes, you can directly modify or add dependency in the package.json but make sure added dependency and version available. ☝☝Question: Finally, how we should include external modules in our code?

var _ = require("lodash");

There is no special method to include external modules, it is same as node internal modules. I have used _ as the variable name since lodash is usually initialized with underscore however you can use any other variable name for lodash and it holds good for any other package. ☝☝Question: Is it fine to start a variable name with _?

Yes, Variable names can contain letter, digits, underscores and dollars sign. It must begin with letters, underscore or dollar sign. Javascript keywords cannot be used as variable name.

our index.js after addition of lodash module.

const http = require('http');
var _ = require('lodash');

const hostname = 'localhost';
const port = 3000;

const server = http.createServer((req, res) => {
res.end('Hello World\n');

server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);

In this blog, we have discussed semantic versioning and addition of external node modules into our application. Let’s discuss more coding in next blog NPM Demystified Part-3.

If you enjoyed this article, please share with your developer friends. Thanks for reading.