try to writing to no exit pipe

Thanks for fixed #76 . I use v5.1.1 and run the same pipe code

onchange -v \"**/*/*.scss\" \"**/*/*.css\" -o \"> task/css.txt\" -- echo {{changed}}

css.txt still no content and I get those message

> onchange -v "**/*/*.scss" "**/*/*.css" -o "> task/css.txt" -- echo {{changed}}

onchange: watching **/*/*.scss, **/*/*.css
onchange: "mobile\test\css\style-edit.css" -> change
onchange: executing outpipe "E:\Program Files\nodejs\node.exe E:\Snow.Huang\project\dev\CampaignBuildTool\node_modules\onchange\echo.js > task/css.txt"
onchange: executing command "echo mobile\test\css\style-edit.css"
onchange: "mobile\test\css\style-edit.css" -> change
'E:\Program' ���O�����Υ~���R�O�B�i���檺�{���Χ妸�ɡC
onchange: outpipe completed with 1
程序嘗試寫入到一個不存在的管道。(try to writing to no exit pipe)
onchange: command completed with 0

after I try running this code

onchange -v \"**/*/*.scss\" \"**/*/*.css\" -o \"echo {{changed}} > task/css.txt\"

css.txt is witted and exit code looks fine!

> onchange -v "**/*/*.scss" "**/*/*.css" -o "echo {{changed}} > task/css.txt"

onchange: watching **/*/*.scss, **/*/*.css
onchange: "mobile\test\css\style-edit.css" -> change
onchange: executing outpipe "echo mobile\test\css\style-edit.css > task/css.txt"
onchange: outpipe completed with 0

what’s happen in first code?

[blakeembrey]

@betsu Thanks! That makes sense. Looks like an escaping issue, I’ll look into how to better fix that.

[betsu]

Hi @blakeembrey, v4 have same problem and message for me. 5.1.2 it’s work fine! but still have one problem: I use win10. when ${process.execPath} has space in string that make error for me.

onchange: watching **/*/*.{scss,css}
onchange: "css\style-edit.css" -> change
onchange: executing outpipe "E:\Program Files\nodejs\node.exe E:\Snow.Huang\project\dev\CampaignBuildTool\node_modules\onchange\echo.js > task/css.txt"
onchange: executing command "echo css\style-edit.css"
'E:\Program' ���O�����Υ~���R�O�B�i���檺�{���Χ妸�ɡC
onchange: outpipe completed with 1
onchange: command completed with 0

try to writing to no exit pipe looks fixed! then I try to fixed ${process.execPath} problem with add double quotes

const ECHO_CMD = `${process.execPath} ${resolve(__dirname, 'echo.js')}
to
const ECHO_CMD = `\"${process.execPath}\" ${resolve(__dirname, 'echo.js')}

and running.

> onchange -v --await-write-finish -o "> task/css.txt" "**/*/*.{scss,css}" -e "**/*/{style,style-source}.css" -- echo {{changed}}

onchange: watching **/*/*.{scss,css}
onchange: "css\style-edit.css" -> change
onchange: executing outpipe ""E:\Program Files\nodejs\node.exe" E:\Snow.Huang\project\dev\CampaignBuildTool\node_modules\onchange\echo.js > task/css.txt"
onchange: executing command "echo css\style-edit.css"
onchange: command completed with 0
onchange: outpipe completed with 0

Oh! success!!

P.S. In line 68 childOutpipe.stdin.end() maybe change to this.childOutpipe.stdin.end()