On Tuesday, 4 October 2016 at 18:41:16 UTC, FreeSlave wrote:
On Tuesday, 4 October 2016 at 17:02:34 UTC, Adam D. Ruppe wrote:
On Tuesday, 4 October 2016 at 16:55:22 UTC, Andre Pany wrote:
Spawn process is working fine on linux, only on windows it
doesn't work.
I will create a bug report.
On Tuesday, 4 October 2016 at 17:02:34 UTC, Adam D. Ruppe wrote:
On Tuesday, 4 October 2016 at 16:55:22 UTC, Andre Pany wrote:
Spawn process is working fine on linux, only on windows it
doesn't work.
I will create a bug report.
This isn't really a bug if it is a cmd file like the other
On Tuesday, 4 October 2016 at 16:55:22 UTC, Andre Pany wrote:
Spawn process is working fine on linux, only on windows it
doesn't work.
I will create a bug report.
This isn't really a bug if it is a cmd file like the other poster
said... cmd files are scripts that need to be run through the
On Tuesday, 4 October 2016 at 13:18:45 UTC, Adam D. Ruppe wrote:
Are you sure npm is in the path? From your shell, do `which
npm` and see where it is coming from, you might want to use the
full path to spawn process.
Yes, npm is in path. From all directories I can execute npm/node
On Tuesday, 4 October 2016 at 12:58:19 UTC, Andre Pany wrote:
Hi,
I need to call a Node application. node and npm are in windows
path variable.
I have following folder structure:
./app.d
./js/helloworld.js
./js/package.json
[...]
npm is .cmd file on Windows. Maybe this is issue. Looks like
Are you sure npm is in the path? From your shell, do `which npm`
and see where it is coming from, you might want to use the full
path to spawn process.
Hi,
I need to call a Node application. node and npm are in windows
path variable.
I have following folder structure:
./app.d
./js/helloworld.js
./js/package.json
content of helloworld.js:
console.log('hello world');
content of package.json:
{
"name": "test",
"version": "1.0.0",
