You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2018. It is now read-only.
I am using bootstrap less files in this build script.my build script is getting compiled successfully and I am getting error in style-concat.css "[ERROR] Syntax Error on line 883 (line:883, column:11)", I have trace the Issue and found in bootstrap less files mixins.less line number 578 uses nested selector syntax ".span@{index}" which is not parsed by the .jar file and ERROR is as it is pasted in style-concat.css, is there any way we can fail the build if we get any syntax error (or defined error options in properties files) in less file or css file. so that we can easily debug and trace the error to fix. everything else is working as expected.
your help will be appreciated.
Thanks,
mehul.
The text was updated successfully, but these errors were encountered:
We actually discussed just this at work last week for the exact same reason. I'll take a look this week and pull it back into the project if I sort it out. It should be possible.
Files names are included in less.js > 1.3.1, we just need to trap these in the build-process and send them to STDOUT. I will put together a pull request for this issue, as it has also befuddled me.
Hi,
I am using bootstrap less files in this build script.my build script is getting compiled successfully and I am getting error in style-concat.css "[ERROR] Syntax Error on line 883 (line:883, column:11)", I have trace the Issue and found in bootstrap less files mixins.less line number 578 uses nested selector syntax ".span@{index}" which is not parsed by the .jar file and ERROR is as it is pasted in style-concat.css, is there any way we can fail the build if we get any syntax error (or defined error options in properties files) in less file or css file. so that we can easily debug and trace the error to fix. everything else is working as expected.
your help will be appreciated.
Thanks,
mehul.
The text was updated successfully, but these errors were encountered: