Atom Integrated Terminal does not behave the same as Windows CMD outside of Atom

[kickthedragon]

So this is a very strange error that's occurring for me. The integrated terminal in atom does not behave the same way as CMD or windows PowerShell outside of Atom.

Background Info: I'm developing a nodejs app with yeomen's angular-fullstack generator. My work computer at home runs linux where this package works perfectly as expected. But my workstation at work runs Windows 10 and figured this package would behave the same way. I've also tried configuring the integrated terminal to test both the Windows Powershell and CMD to make sure the same error is reproduced and I can confirm the issue is whether or not the terminal being used is integrated in Atom or running separately.

Problem: When I run gulp serve or npm install with the terminal configured to use CMD.exe or PowerShell.exe within atom, the command does not perform as expected. If i run either command in their respective independent application / window (cmd.exe or plowershell.exe) the commands work perfectly (just as if I was in a linux bash). But when I use your package within atom and configured to use either shell, npm install does not completely install all the modules (specifically non of the dev dependencies). So I ran npm install in a separate cmd.exe which installed all the modules to see if this was the only issue, but when when I run gulp serve within the tokamak-terminal i get a syntax error saying Unexpected token and its highlighting import express from express . This does not happen when i run gulp serve in a cmd.exe or windows powershell.exe independently, my nodejs app launches as expected.

Let me know if theres any logs or anything else i can contribute to debug this. Having a terminal within atom is highly convenient so if this is a quick fix i'd love to make sure i give you enough info to do it. The package works perfectly on my linux box.