Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Output ends with __ESCAPED_SOURCE_END_CLEAN_CSS__

See original GitHub issue

I have a vendor-provided CSS file which I am using grunt-contrib-cssmin (^1.0.1) to strip out comments and minify.

The file is processed, and the output ends with __ESCAPED_SOURCE_END_CLEAN_CSS__.

A sample of the vendor file I am processing is attached (had to change file ext. to .txt so it would upload, but I am dealing with the same file with ext. .css).

Is there anything in this sample file that would cause the processing to add this output?

Cheers 😄 player.txt

Issue Analytics

State:
Created 7 years ago
Comments:5

Top GitHub Comments

1reaction

jakubpawlowiczcommented, Dec 19, 2016

Thanks to the new tokenizer this is no longer an issue. Added a test case and marking it as fixed on master. Thanks @davewallace!

0reactions

davewallacecommented, Dec 20, 2016

For my part, I was dealing with vendor contributed files which we did not want to touch anyway, so whether it was a parsing error which resulted in the __ESCAPED_SOURCE_END_CLEAN_CSS__ or not, the point is moot as we wouldn’t change a given error to avoid the problem apparent in this issue.

Thinking back though, I seem to recall removing some comments via minification which removed the error… this is a while ago for me now, done a lot of things since, so I may be incorrect there.