#431: fixed build command

[hohwille]

Fix for #431

[hohwille]

As discussed offline there have been issues when node_modules have not been present. This was previously silently adding install as goal to the build-tool. However, unlike tools like mvn for npm or yarn this was entirely incorrect as

npm install build

means something totally different than

npm install
npm build

In JS build tools goals can also be followed by parameters such as

npm add «pacakge»

Therefore npm install build is thinking that the dependency build should be installed and even adds this to the package.json as dependency leading to silly results. It took me while to understand these worlds of JS. Would have been easier if some domain expert had created the commandlets initially.

[hohwille]

OK, for some odd reason tr '\n' '§' is not working in git-bash (on windows).
Therefore we had to use sed magic. To avoid redundancy of this kind of tricky detection inside package.json, I moved it to functions and share it between npm and yarn commandlets.

Also I found and fixed another small bug that debug option (-d or --debug) was not passed by doDevonCommand. Therefore without this fix devon build -d was not printing debug info while devon yarn -d build did. With the fix both behave the same.

[markusschuh]

Introducing a non-ASCII char like '§' into the stream has an influence on the "binary detection" logic built into grep - and this is dependent on the shell environment, since the intention of this check is to avoid output of binary as potentially non-printable chars inside grep output. So an additional "-a" option (treat all files as ASCII text) to grep would harden the code more against such environment differences.

But since both npm and yarn have node as prerequisite - hence a more powerful scripting language is available - it might make more sense to do the check with javascript:

node -e "process.exit(require('./package.json').scripts.hasOwnProperty('build'));"

Tested successfully also with an a bit older node 10.x