Draw a text-based graphical representation of the commit history on the left hand side of the output. This may cause extra lines to be printed in between commits, in order for the graph history to be drawn properly

git log --oneline --all --graph

When --graph is not used, all history branches are flattened which can make it hard to see that the two consecutive commits do not belong to a linear branch

We can add part of changes (from the same file) to the staging area and not to add the rest of the changes

git add -p

It will ask us interactively whether we want to add each individual changes to the staging area or not

y

means yes,

n

means no

Starts the process

git bisect start

install/uninstall modules/packages

create & share modules

use packages created by other developers

manage dependencies & versioning

Shows the current version of NPM

npm --version

Short version of the above command

npm -v

Shows

help

page with some useful information about how to use

npm

npm

Same as the above command

npm help

Creates

package.json

file that contains all of the settings and essential information for the application Creates the file with the default values

npm init -y  /  npm init --yes

Main properties / parameters that the file includes:

name

- name of the app (default is the name of the current folder)

version

- version of the app (default is 1.0.0 - major.manor.patch)

description

- short description for the project

main

- entry point - main JS file

keywords

- keywords that the app is related to

author

- project author

license

- default is ISC (Internet Systems Consortium)

Sets default value for author property of

package.json

file

npm config set init-author-name "Va. Tand."

We can omit

config

keyword

npm set init-author-name "Va. Tand."