Buggy backslash escaping behavior?

[ClementParis016]

Testing on both Node.js v0.12.5 and v5.0.0 on Windows, I'm encountering a strange behavior regarding backslashes. Take a look at the following I typed in the Node CLI:

> '\/'
'/'
> '\\/'
'\\/'

Here is the same thing typed in Google Chrome 46's console:

> '\/'
'/'
> '\\/'
'\/'

So, as you can see on the last lines, the escaping of backslashes doesn't seem to be correct on the Node environment. Is it something known and expected or actually a bug?

[Fishrock123]

I think there was another issue for this, but can't seem to find it right now. :/

[targos]

Here it is: #3240

[ClementParis016]

Ok, thanks for your help. It's a bit confusing that every web browser behaves the same way and Node has a different behavior for this.

So, how should I proceed if I want to get a single backslash, since \\ gives me two?

[targos]

It doesn't give you too backslashes. It's just the REPL output that's different.
You can see with console.log('\\'); that the string contains only one backslash.

[cjihrig]

Closing as a dup of #3240