[BUG] in package.json scripts on Windows, \n gobbles the rest of the script about run-script

[wraithgar]

@nlf I wonder if this has been fixed now that we pulled out puka from dependencies?

This is npm@6

[nlf]

this is a tricky one. we've just released 1.8.0 of this package that switches the string quoting and escaping to use puka however per puka's own documentation there's some weirdness with line breaks in strings:

I searched for days for a way to quote or escape line breaks in arguments to
cmd.exe, but couldn't find one (regular ^-prepending and quotation marks
don't seem to cut it). If you know of a way that works, please open an
issue to tell me about it! Until
then, any line break characters (\r or \n) in values being interpolated by
sh will cause an error to be thrown on Windows only.

this seems to be the sort of thing that there's not a great consistent resolution for. if puka lands a fix, then we'll get it pulled in there, otherwise i think there isn't much we can do reasonably here.

[ruyadorno]

@nlf I wonder if this has been fixed now that we pulled out puka from dependencies?

[ruyadorno]

ooops