Closed mcollina closed 2 years ago
Can you post the full file / directory path (what's being chopped after the a
) and I'll add it to the edge cases / tests PR I'm working on, which includes a lot of funky stuff with Windows paths, Unicode etc
Also which version of Node? The fix for Windows path separators being treated as escape patterns has some issues in Node 8 and different issues in Node 11 that aren't in Node 10
I spoke to @mcollina just now – it's Node 10 (and Windows 10)
if it's in the latest 0x release, https://github.com/davidmarkclements/0x/pull/201 might be related
I think the regexp introduced in https://github.com/davidmarkclements/0x/pull/193/
is not complete/broken on Node 10.
cc @mafintosh
I think this line https://github.com/davidmarkclements/0x/blob/1cfbc5686c8f8cc48bc500a8d31a7c61f00d770a/lib/v8-log-to-ticks.js#L36
needs to change the pattern from :\\
to :\
There's a bunch of issues with that regex that are fixed in the PR I'm working on, for instance it gets confused by unicode chars like //u12a3 - but in my tests I've only seen that happen on Node 8. What's the text after the a
in your path?
Maybe it's mistakenly parsing something like D:/a/n as a newline?
That happens on Azure pipelines. There is nothing else.
was this ever resolved?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.