Node.js - Revision history

M: /* Development */

2023-03-02T17:01:35Z

Development

← Older revision		Revision as of 17:01, 2 March 2023
Line 31:		Line 31:

	{\| class="wikitable"		{\| class="wikitable"
	! [[~~Node create~~ a new module]]		! [[Create a new node module]]
	\|}		\|}
	{\| class="mw-collapsible mw-collapsed wikitable"		{\| class="mw-collapsible mw-collapsed wikitable"

2023-03-02T17:00:37Z

Upgrade

← Older revision		Revision as of 17:00, 2 March 2023
Line 23:		Line 23:
	Don't mess with anything other than lts, you've been warned:		Don't mess with anything other than lts, you've been warned:
	* nvm install --lts		* nvm install --lts

			NOTE that you have to reinstall all global packages, as you have a brand new virgin node installation now.

			Also, you may want to clean up the older ones at some point.

	=== Development ===		=== Development ===

2018-10-14T19:18:21Z

← Older revision		Revision as of 19:18, 14 October 2018
Line 77:		Line 77:
	Warning: I had trouble when globally installing rad-scripts from npm and from my local source; for now I'll avoid [npm install -g rad-scripts].		Warning: I had trouble when globally installing rad-scripts from npm and from my local source; for now I'll avoid [npm install -g rad-scripts].

	I have also had problems with file locking and permissions when tools like Visual Studio Code are running.		I have also had problems with file locking and permissions when tools like Visual Studio Code are running, see ticket [https://github.com/npm/npm/issues/17444 here].

	fixes:		fixes:

2018-10-14T19:10:13Z

@@ Line 70: / Line 70: @@
   npm install -S rad-scripts
 |}
 === Troubleshoot ===

2018-10-14T19:09:04Z

Troubleshoot

← Older revision		Revision as of 19:09, 14 October 2018
Line 98:		Line 98:

	=== Troubleshoot ===		=== Troubleshoot ===
	* After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages:		* After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages. You should be able to run [mh scripts]. Here's what it does:
	cdr && npm install -g; cdm && npm install -g; cdas && npm install -g		cdr && npm install -g; cdm && npm install -g; cdas && npm install -g
	* Reinstallation problems		* Reinstallation problems

2018-10-14T19:08:02Z

@@ Line 23: / Line 23: @@
 Don't mess with anything other than lts, you've been warned:
 * nvm install --lts
 === Troubleshoot ===

2018-10-14T19:06:48Z

Troubleshoot

@@ Line 27: / Line 27: @@
 * After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages:
   cdr && npm install -g; cdm && npm install -g; cdas && npm install -g
 Warning: I had trouble when globally installing rad-scripts from npm and from my local source; for now I'll avoid [npm install -g rad-scripts].
 * If filesystem navigation is slow, loadning npm can be EXTREMELY slow; you can add [ --no-use] to startup, then call [node use] before using it, as a shitty workaround.  I'll keep upgrading npm until it is sane.  It sure has had a rough growing journey.

2018-09-14T20:31:55Z

Troubleshoot

← Older revision		Revision as of 20:31, 14 September 2018
Line 26:		Line 26:
	=== Troubleshoot ===		=== Troubleshoot ===
	* After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages:		* After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages:
	npm install -g ~~rad-scripts~~; cdm && npm install -g; cdas && npm install -g		cdr && npm install -g; cdm && npm install -g; cdas && npm install -g
			Warning: I had trouble when globally installing rad-scripts from npm and from my local source; for now I'll avoid [npm install -g rad-scripts].

	* If filesystem navigation is slow, loadning npm can be EXTREMELY slow; you can add [ --no-use] to startup, then call [node use] before using it, as a shitty workaround. I'll keep upgrading npm until it is sane. It sure has had a rough growing journey.		* If filesystem navigation is slow, loadning npm can be EXTREMELY slow; you can add [ --no-use] to startup, then call [node use] before using it, as a shitty workaround. I'll keep upgrading npm until it is sane. It sure has had a rough growing journey.

2018-02-19T13:18:24Z

← Older revision		Revision as of 13:18, 19 February 2018
Line 23:		Line 23:
	Don't mess with anything other than lts, you've been warned:		Don't mess with anything other than lts, you've been warned:
	* nvm install --lts		* nvm install --lts

			=== Troubleshoot ===
			* After installing a new node version with [nvm install --lts], you'll have to reinstall all node packages:
			npm install -g rad-scripts; cdm && npm install -g; cdas && npm install -g
			* If filesystem navigation is slow, loadning npm can be EXTREMELY slow; you can add [ --no-use] to startup, then call [node use] before using it, as a shitty workaround. I'll keep upgrading npm until it is sane. It sure has had a rough growing journey.

2017-09-01T18:46:52Z

← Older revision		Revision as of 18:46, 1 September 2017
Line 12:		Line 12:
	* nvm ls-remote --lts		* nvm ls-remote --lts
	* nvm install --lts # to get the latest long-term-support release - you can pick a release too if needed, eg 5.8.0)		* nvm install --lts # to get the latest long-term-support release - you can pick a release too if needed, eg 5.8.0)
	* nvm alias default stable		* nvm ls # show what you have
	* the common .bashrc_env should take care of ~~this: update .bashrc to configure~~ node ~~on even non-interactive shells - it should match the restart lines, above~~		* nvm alias default stable # needed?
			* the common .bashrc_env should take care of node setup
	* additional fyi goo		* additional fyi goo
	** nvm use 4.2.1; node -v; nvm ls; nvm alias default 0.11.13; nvm use default		** nvm use 4.2.1; node -v; nvm ls; nvm alias default 0.11.13; nvm use default