DEV Community: Massii

How do I install multiple node js version on the same machine

Massii — Tue, 15 Feb 2022 17:13:05 +0000

In this post, we will get to know and learn about running multiple node js version on the same machine with NVM .

While working on the multiple projects of NodeJs, you might be required to run different projects on the different nodejs version or for the legacy nodejs projects, you might require an old version of the nodejs, and the others required a new version of node-js, or to checkout the new feature of nodejs, you need to install the latest version of node js

As on the same machine, we can only install one version of the nodejs, so it's very painful to uninstall and install the new node version as per your project requirements.

To overcome this problem, we can use the Node Version Manager (NVM). NVM allows installing multiple node js versions on the same machine and switching between the required node js version.

Installation of NVM

Windows

Download the latest version of NVM

https://github.com/coreybutler/nvm-windows/releases/latest

Download nvm-setup.zip and install on the windows

Verify Installation

nvm version

MacOs/Linux

Using curl

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash

Using Wget

wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash

Verify Installation

command -v nvm

Usage

Get a List of all available NodeJs versions

nvm ls available //windows
nvm ls-remote //MacOs/Linux

Install latest NodeJs version

nvm install node

Install latest LTS Release

nvm install --lts

Install particular NodeJs version

Multiple NodeJs version can be installed using the below command.

nvm install 8.11.1 // to install the 8.11.1 version

UnInstall the multiple NodeJs version

nvm uninstall 8.11.1

Switching the NodeJs version

nvm list //for windows
nvm ls //for MacOs/linux

Switching Between installed NodeJs Versions

nvm use 8.11.1 //To enable 8.11.1
nvm use 12.13.1 //To enable 12.13.1

Full Article

Git-Flow vs Github-flow

Massii — Sat, 12 Feb 2022 17:49:24 +0000

Git-flow

Git-flow was described by Vincent Driessen on his 2010 post A successful Git branching model. I’ve found it to be a great way to organize a repository. In short, you:

Keep your master branch as the code that has been released,
Use a develop branch as the current “snapshot” of what will go into the next release - your living beta,
Spawn off feature branches off develop for every new feature, which are merged back into it when they’re ready,
When you are ready to release, you merge to master and tag with a release version.

There are other considerations for how to deal with hotfixes, but that’s the gist of it. You can see a git-flow diagram below:

This is a great approach and it has several advantages:

master always remains as a stable reflection of your live code,
You can trivially do hotfixes without worrying about unfinished features,
Feature branches ensure that teams working in parallel don’t trip over each other and that conflicts need to be handled only once (the moment the feature is done),
It allows teams to cherry-pick changes other teams may be doing on their feature branches, without needing these commits to be on develop already,
It lets you do a release off develop at any point - if a feature isn’t ready, that’s OK, you just leave it for the next release.

There are helper scripts to assist you with Gitflow. Atlassian’s SourceTree supports it directly as well.

Github-flow

Proponents of Github-flow (and its cousin Gitlab-flow) have a few complaints about it. The main argument is that it goes against continuous delivery, since at some point someone needs to “flip a switch” and do a release from develop into master.

That’s a valid argument. Nothing is less continuous than manual switch-flipping.

The Github-flow proposal is that you should:

Do away with the develop branch altogether,
Spawn all feature branches off master, and merge them back into master when ready,
Version tagging should not be carried by a human, but by an automated process whenever code is pushed to live,

These are valid points and they do result on a lighter-weight workflow. But they ignore that there are cases where you want a manual release, a negotiation of what is supposed to go into any particular version.

My take on it

Both systems have their uses. I think something like Github-flow is a great approach if what you are developing is an application. On that case, just using a master branch plus features branches works well, and you can do your releases in an automated fashion. The deployment itself is the atomic end-product you care about.

When you are building a library, where people outside your team might depend on specific versions, I think git-flow is the right approach. For a library, you want to lump your versioned changes together into a conceptual unit - including potentially separating or delaying breaking changes. At this point, coming to an agreement on what should go into a version makes sense, as does the manual release process of git-flow.

If anybody outside of your team depends on your versioning scheme, or will need to have a clear conceptual overview of what changed on a particular release, I’d recommend using git-flow.

If whatever you are releasing is the final artifact, and it will be used but others will not need to reference its version, then GitHub-flow does the trick.

Source

Top 5 vscode themes

Massii — Sat, 12 Feb 2022 10:36:58 +0000

1 : Ayu theme

Download

2 : Material darker

Download

3 : deepdark material

Download

4 : Andromeda theme

Download

5 : Atom one dark

Download

follow me

Github

Conventional Commits 1.0.0

Massii — Fri, 11 Feb 2022 17:04:54 +0000

Summary

The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.

The commit message should be structured as follows:

type [ optional scope ] : description

[optional body]

[optional footer(s)]

The commit contains the following structural elements, to communicate intent to the consumers of your library:

1- fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).

2- feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).

3- BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.

4- types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.

5- footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format.

Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

Examples

Commit message with description and breaking change footer
feat: allow provided config object to extend other configs
BREAKING CHANGE: extends key in config file is now used for extending other config files

Commit message with ! to draw attention to breaking change
feat!: send an email to the customer when a product is shipped

Commit message with scope and ! to draw attention to breaking change
feat(api)!: send an email to the customer when a product is shipped

Commit message with both ! and BREAKING CHANGE footer
chore!: drop support for Node 6
BREAKING CHANGE: use JavaScript features not available in Node 6.

Commit message with no body
docs: correct spelling of CHANGELOG

Commit message with scope
feat(lang): add polish language

Commit message with multi-paragraph body and multiple footers
fix: prevent racing of requests
Introduce a request id and a reference to latest request. Dismiss incoming responses other than from latest request.
Remove timeouts which were used to mitigate the racing issue but are obsolete now.
Reviewed-by: Z
Refs: #123

Specification

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

1- Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.

2- The type feat MUST be used when a commit adds a new feature to your application or library.

3- The type fix MUST be used when a commit represents a bug fix for your application.

4- A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., fix(parser):

5- A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., fix: array parsing issue when multiple spaces were contained in string.

6- A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.

7- A commit body is free-form and MAY consist of any number of newline separated paragraphs.

8- One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a :< space > or < space ># separator, followed by a string value (this is inspired by the git trailer convention).

9- A footer’s token MUST use - in place of whitespace characters, e.g., Acked-by (this helps differentiate the footer section from a multi-paragraph body). An exception is made for BREAKING CHANGE, which MAY also be used as a token.

10- A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.

11- Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.

12- If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., BREAKING CHANGE: environment variables now take precedence over config files.

13- If included in the type/scope prefix, breaking changes MUST be indicated by a ! immediately before the :. If ! is used, BREAKING CHANGE: MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.

14- Types other than feat and fix MAY be used in your commit messages, e.g., docs: updated ref docs.

15- The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.

16- BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.

Why Use Conventional Commits

Automatically generating CHANGELOGs.
Automatically determining a semantic version bump (based on the types of commits landed).
Communicating the nature of changes to teammates, the public, and other stakeholders.
Triggering build and publish processes.
Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.

Credits to conventionalcommits.

Follow me

Follow me on Github.

DEV Community: Massii

How do I install multiple node js version on the same machine

Installation of NVM

Windows

MacOs/Linux

Usage

Install particular NodeJs version

UnInstall the multiple NodeJs version

Switching the NodeJs version

Switching Between installed NodeJs Versions

Git-Flow vs Github-flow

Git-flow

Github-flow

My take on it

Top 5 vscode themes

1 : Ayu theme

2 : Material darker

3 : deepdark material

4 : Andromeda theme

5 : Atom one dark

follow me

Conventional Commits 1.0.0

Summary

Examples

Specification

Why Use Conventional Commits

More

Follow me