Parser Misrepresentation of Escaped Newlines Alters Positional Data in AST and Stylelint Reports

[blyedev]

The current parser does not have the capability to represent JavaScript string literal escaped newlines (\n) in the AST differently from traditional newlines. As a result, during output, escaped newlines are converted into literal newlines, altering their position in the file. This change causes downstream issues with tools such as Stylelint, which rely on accurate positional data for reporting, leading Stylelint to report errors as if they occur elsewhere in the file.