Add quoting around data_sync_id and visitor_data

[Brainicism]

No description provided.

[ryneeverett]

Not sure what the intent is but I'd be surprised if this fixed anything. Per the subprocess docs:

Providing a sequence of arguments is generally preferred, as it allows the module to take care of any required escaping and quoting of arguments (e.g. to permit spaces in file names).

My reading is that without shell=True there should be no possibility of word splitting or interpolation here.

[Brainicism]

Not sure what the intent is but I'd be surprised if this fixed anything. Per the subprocess docs:

Providing a sequence of arguments is generally preferred, as it allows the module to take care of any required escaping and quoting of arguments (e.g. to permit spaces in file names).

My reading is that without shell=True there should be no possibility of word splitting or interpolation here.

Good catch! I assumed that there was interpolation here because of #47 (comment), where it looks like the data_sync_id is being split at the |. Regardless of if it fixes anything, its probably better to quote these anyway for convention anyway

[ryneeverett]

IMO it's pretty unconventional to quote arguments passed to subprocess because, as the docs say, subprocess takes care of it. I have to believe that it's highly unlikely you've encountered a bug in such a widely used module so I'd suggest exploring more probable root causes.

While I admit that is odd looking I wonder if the pipes are an oddity of the OP's terminal emulator truncating a long line. (Are pipes even valid characters in a data_sync_id?) Regardless I think you're on a better track exploring the OP's node environment because that javascript SyntaxError does seem like the real root cause.