babel-node not recognized as internal or external command

[imsam67]

I'm following along the tutorial on PluralSight for React with ES6 and Redux. I'm using Visual Studio Code as my editoe. When I add babel-node in the start script, I get

babel-node not recognized as internal or external command

Any idea why?

[coryhouse]

Have you run npm install? What version of node and npm are your running? What OS?

[imsam67]

Yes, I have run npm install
I'm running node version 6.3.1 and npm 3.10.9. I'm running this on a Windows 10 machine build 14393.321

I got all this information using the built-in terminal in Visual Studio Code from inside the project folder -- except Windows 10 build.

Also if I run npm list babel-node from the terminal, I get (empty) so it doesn't seem to be installed. By the way, babel-node is not in package.json either.

[coryhouse]

Like you, npm list babel-node returns nothing for me, but it works because it's bundled with babel.

If you look in node_modules/.bin, you should see a babel-node folder. Do you?

[pddigital]

Same problem for me with Windows 10...
No babel-node is installed.
Nothing under .bin.

[imsam67]

There is no babel-node folder inside "node_modules" or "node_modules/.bin"

I'm attaching a screen shot of the .bin folder under node_modules

[pddigital]

Ditto for me. No babel-node in the bin directory. I sort of got it to work by installing babel-cli globally but now it doesn't recognize anything in the package.json, so that's not a fix.

[coryhouse]

That's bizarre. I've just tried it in the terminal in the latest version of Visual Studio Code and on the native terminal in Windows 10. It works just fine in both.

Are you all using the project completely unchanged? I simply cloned this repo on Windows 10 and it worked. I'm using Node 6.3 as well.

[imsam67]

I didn't clone the project. I'm creating the files/folders as I go through the PluralSight video. The only difference is that instead of using WebStorm, I'm using Visual Studio Code.

[pddigital]

node v6.5, npm v3.10.3, Atom... Windows 10. I just deleted and recloned the directory, npm installed, npm started, same deal.

[pddigital]

I downgraded node to 5.14 and it works! Thanks. That was actually in the readme. Windows has a problem with Node 6.

[coryhouse]

Good to hear you're rolling Paul. The frustrating thing is Node 6 works fine on some Windows machines. I'd like to figure out why some Windows machines are failing, but I haven't been able to reproduce on any of my Windows boxes.

[coryhouse]

@imsam67 Have you tried running Node 5 instead? That has resolved the issue for some others on Windows.

[imsam67]

It didn't work for me. See the image below

I don't know how Paul was able to go down to 5.14. I don't see that version even listed here:
https://nodejs.org/en/download/releases/

[imsam67]

Interestingly, if I download the whole project from GitHub and run npm install, I do end up with babel-node in .bin and npm start -s works fine

Not sure why when I was simply following the video and created things step by step, it didn't work. Possibly skipping something unintentionally

[coryhouse]

Interesting. I recommend avoiding paths with a space. Also, if downloading this project from github works fine, then I'd be interested to know what's different with your hand built version. Did you perform a diff? Alternatively, can you post it on Github?