Repository navigation
normalizeSlashes should probably no-op on *nix #44174
Description
Activity
It would probably be best practice to warn or even error if any paths provided in config files or source code contain back slashes, with a note that they will have different behavior depending on OS.
David Michon (@dmichon-msft) Related to that statement: #44053
I tried this out in #53173 and I didn't see much of a difference; perhaps we've optimized it enough that this turns out to not be a problem anymore. But, I might be lacking a test case where this is really bad.
As David Michon (@dmichon-msft) pointed out, Linux file names can contain backslashes, so indiscriminately converting them into forward slashes is probably a bad idea. Redefining
normalizeSlashesas the identity function on non-Windows platforms would also be a perf win, since it's very hot code. The biggest concern is that someone might be depending on this (e.g. I think you can use backslashes in paths in tsconfig.json).