It appears to. But hold it: Is it node.js at fault or your good self?
Its probably you, dear earthling. yet again, you got mixed up and now, when you type
> node main.js,
it rudely answers:
'node' is not recognized as an internal or external command !
After going all over and getting excruciatingly detailed help on how to set up a PATH statement in Windows (as if you were a students of Computer 101), you are ready to pull out all your (remaining?) hair (its actually easier to cut by the way, and less painful).
However, check this most simple possibility: You clicked the wrong button during your installation.
Watch and learn:
1. Step 1: Download the 32bit or 64bit node.js installer file
2. Launch the installer and you get the following:
So much hair lost for so little... But who to blame except your selves for not carefully studying the options?
Therefore, if you have this frustrating problem reinstall node.js and carefully observe the commandments.
Surely much hair will be saved - from being uprooted that is, not from the fires and worms of the valley of Ben Hinnom: that's an entirely separate matter.
Bon Voyage, mes frères et mes sœurs
Its probably you, dear earthling. yet again, you got mixed up and now, when you type
> node main.js,
it rudely answers:
'node' is not recognized as an internal or external command !
After going all over and getting excruciatingly detailed help on how to set up a PATH statement in Windows (as if you were a students of Computer 101), you are ready to pull out all your (remaining?) hair (its actually easier to cut by the way, and less painful).
However, check this most simple possibility: You clicked the wrong button during your installation.
Watch and learn:
1. Step 1: Download the 32bit or 64bit node.js installer file
2. Launch the installer and you get the following:
3. Problems may occur in the next screens that looks like this:
4. If you click on the little arrow in each button, its important to read the options offered as illustrated below:
The options are:
- Will be installed on local hard drive
- Entire feature will be installed on local hard drive [preferred choice]
- Feature will be installed when required [trouble!!]
The options in the screen blow are more expansive but note that the safest options is still: Entire feature will be installed on local hard drive
5. If you chose "Feature will be installed when required" you are looking for serious trouble because Windows is very unlikely to do as promised - it will NOT install the features when required, therefore, node.exe will be absent and hence the message "'node' is not recognized as an internal or external command !"
It's that simple.
Therefore, if you have this frustrating problem reinstall node.js and carefully observe the commandments.
Surely much hair will be saved - from being uprooted that is, not from the fires and worms of the valley of Ben Hinnom: that's an entirely separate matter.
Bon Voyage, mes frères et mes sœurs
Comments
Post a Comment