DevOps Tools/Repository Management/npm - Revision history

R00t: /* Local */

2019-10-15T21:29:41Z

‎Local

R00t at 21:29, 15 October 2019

2019-10-15T21:29:26Z

R00t at 21:26, 15 October 2019

2019-10-15T21:26:18Z

R00t: /* Local vs Global */

2019-10-15T21:18:19Z

‎Local vs Global

R00t: /* Local vs Global */

2019-10-15T21:07:58Z

‎Local vs Global

R00t at 15:26, 15 October 2019

2019-10-15T15:26:33Z

R00t at 20:48, 14 October 2019

2019-10-14T20:48:21Z

R00t at 20:13, 14 October 2019

2019-10-14T20:13:16Z

R00t: Created page with "=npm="

2019-10-14T20:12:24Z

Created page with "=npm="

New page

=[[DevOps_Tools/Repository_Management/npm|npm]]=

@@ Line 70: / Line 70: @@
   <nowiki>~$ npm init --y</nowiki>
 Whenever you install a new package, it will update the <code>package.json</code> file.
-  <nowiki>~$ $ npm install underscore
+  <nowiki>~$ npm install underscore
 npm notice created a lockfile as package-lock.json. You should commit this file.
 npm WARN nodedemo@1.0.0 No description

← Older revision		Revision as of 21:29, 15 October 2019
Line 64:		Line 64:
	├── npm@6.9.0		├── npm@6.9.0
	└── uglify-js@3.5.3</nowiki>		└── uglify-js@3.5.3</nowiki>
		+
		+	==Local==
		+	Most of the time you will install packages locally using a <code>package.json</code> file.<br>
		+	Create a <code>package.json</code> file.
		+	<nowiki>~$ npm init --y</nowiki>
		+	Whenever you install a new package, it will update the <code>package.json</code> file.
		+	<nowiki>~$ $ npm install underscore
		+	npm notice created a lockfile as package-lock.json. You should commit this file.
		+	npm WARN nodedemo@1.0.0 No description
		+	npm WARN nodedemo@1.0.0 No repository field.
		+
		+	+ underscore@1.9.1
		+	added 1 package from 1 contributor and audited 1 package in 7.264s
		+	found 0 vulnerabilities</nowiki>

← Older revision		Revision as of 21:26, 15 October 2019
Line 41:		Line 41:
	:installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>. A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.		:installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>. A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.
	'''NOTE:''' regarding global packages, you ''can'' use <code>npm config</code> to change the directory prefix to somewhere '''not''' owned by root, such as <code>$HOME</code>, however in most modern deployments you'll be using npm in an ephemeral container where the user is already root. It should also be noted that most packages that are installed globally, like CLI, are used by the developer in a manual fashion rather than in an automated deployment.		'''NOTE:''' regarding global packages, you ''can'' use <code>npm config</code> to change the directory prefix to somewhere '''not''' owned by root, such as <code>$HOME</code>, however in most modern deployments you'll be using npm in an ephemeral container where the user is already root. It should also be noted that most packages that are installed globally, like CLI, are used by the developer in a manual fashion rather than in an automated deployment.
		+
		+	=Package Installation=
		+	==Global==
		+	Global packages are installed with the <code>--global</code> flag.
		+	<nowiki>~$ npm install uglify-js --global</nowiki>
		+	You can list them using:
		+	<nowiki>$ npm list --global
		+	home/user/.node_modules_global/lib
		+	├─┬ npm@6.9.0
		+	│ ├── abbrev@1.1.1
		+	│ ├── ansicolors@0.3.2
		+	│ ├── ansistyles@0.1.3
		+	│ ├── aproba@2.0.0
		+	│ ├── archy@1.0.0
		+	....................
		+	└─┬ uglify-js@3.5.3
		+	├── commander@2.19.0
		+	└── source-map@0.6.1
		+
		+	~$ npm list -g --depth=0
		+	/home/user/.node_modules_global/lib
		+	├── npm@6.9.0
		+	└── uglify-js@3.5.3</nowiki>

← Older revision		Revision as of 21:18, 15 October 2019
Line 40:		Line 40:
	;Global		;Global
	:installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>. A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.		:installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>. A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.
		+	'''NOTE:''' regarding global packages, you ''can'' use <code>npm config</code> to change the directory prefix to somewhere '''not''' owned by root, such as <code>$HOME</code>, however in most modern deployments you'll be using npm in an ephemeral container where the user is already root. It should also be noted that most packages that are installed globally, like CLI, are used by the developer in a manual fashion rather than in an automated deployment.

@@ Line 37: / Line 37: @@
 ==Local vs Global==
 ;Local
-:installs the package in a <code>node_modules</code> in your parent working directory. In general, all packages should be installed locally.  This allows you to have dozens of the same applications on your computer, all running a different version of each package if needed.
+:installs the package in a <code>node_modules</code> in your parent working directory. '''In general, all packages should be installed locally.'''  This allows you to have dozens of the same applications on your computer, all running a different version of each package if needed.
 ;Global
 :installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>.  A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.

← Older revision		Revision as of 15:26, 15 October 2019
Line 29:		Line 29:
	undefined		undefined
	> .exit</nowiki>		> .exit</nowiki>
		+
		+	=Update=
		+	==CentOS==
		+	<nowiki>~$ npm install npm@latest -g</nowiki>
		+
		+	=Node Modules=
		+	==Local vs Global==
		+	;Local
		+	:installs the package in a <code>node_modules</code> in your parent working directory. In general, all packages should be installed locally. This allows you to have dozens of the same applications on your computer, all running a different version of each package if needed.
		+	;Global
		+	:installs the package in <code>{prefix}/lib/node_modules</code> which is owned by root (where <code>{prefix}</code> is usually <code>/usr/ or /usr/local/</code>. A package should be installed globally when it provides an executable command that you run from the shell and is reused across projects.

← Older revision		Revision as of 20:48, 14 October 2019
Line 1:		Line 1:
	[[DevOps_Tools/Repository_Management/npm\|npm]]		[[DevOps_Tools/Repository_Management/npm\|npm]]
		+	=Overview=
		+	'''npm''' is the Node Package Manager. It provides access to a whole ecosystem of Node-based tools for developers to use when creating a server environment for applications or simply to aid them in local task automation. It is also commonly used with CI tools like Jenkins to automate build, test, prod, and other phases.
		+
		+	=Installation=
		+	[https://github.com/nodesource/distributions/blob/master/README.md https://github.com/nodesource/distributions/blob/master/README.md]
		+	==Ubuntu==
		+	<nowiki>~$ curl -sL https://deb.nodesource.com/setup_12.x \| sudo -E bash -
		+	~$ sudo apt-get install -y nodejs</nowiki>
		+
		+	==CentOS==
		+	<nowiki>~$ sudo curl -sL https://rpm.nodesource.com/setup_12.x \| bash -</nowiki>
		+
		+	=Verify Installation=
		+	<nowiki> ~$ which node
		+	/usr/bin/node
		+	~$ node --version
		+	v12.11.1
		+	~$ which npm
		+	/usr/bin/npm
		+	~$ npm --version
		+	6.11.3</nowiki>
		+	Make sure Node is working properly.
		+	<nowiki>~$ node
		+	Welcome to Node.js v12.11.1.
		+	Type ".help" for more information.
		+	> console.log('Node is running')
		+	Node is running
		+	undefined
		+	> .exit</nowiki>

← Older revision		Revision as of 20:13, 14 October 2019
Line 1:		Line 1:
−	=[[DevOps_Tools/Repository_Management/npm\|npm]]=	+	[[DevOps_Tools/Repository_Management/npm\|npm]]