-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minify Directory on CSS goes on error: Minify Failed #41
Comments
I also have this problem on macOS 10.14.4 with VSCode 1.33.1. Trying to minify a directory with even a single css file in will result in a failure with "Minify failed: 1 error(s)". The number of errors is just the number of css files in the directory. Directories that previously worked fine no longer minify. This possibly happened after upgrading to 10.14.4 but I'm not 100% sure. If I dump the error to console at about line 178 of extension.js I get:
however .... if I just comment out the line at 168 of extension.js that is removing the absolute file path:
then everything works fine. The directory is minified with no errors. No idea why we need to keep the absolute path now but hope that's some help. Let me know if I can provide any more info. s. |
Same on Windows 10 VSCode 1.33.1. Commenting out line 168 worked for me as well |
@millipedia @reevet - How do you modify the source code EDIT: For windows it's in: |
I'm having the same error, and commenting out that line solved it. |
Commenting out that line solves the problem, but there is another issue. In the minified file paths would be incorrect. for example If you have CSS like this: In output file would be like this: So, then you must replace in the outputted file all "d:/Projects/test/styles" with "..". |
Just set the setting "rebase" to false. Thats should fix that. |
A little bit late, but anyhow ... |
Hello,
I have an issue on a minifying directory with CSS files on Windows 10 with VSCode 1.33.1.
It goes on error: "Minify failed: 2 error(s).
It works on JS and single CSS files.
The text was updated successfully, but these errors were encountered: