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
Sorry if this is not appropriate to be marked as an issue. I thought this may be an appropriate place as I'm specifically wondering about debugging LESS when using less-rails(.css.less files).
How do you debug errors in your .css.less file?
If I simply forget a semicolon in the file, when I load the file in the browser, I get Less:Error at /Unrecognised input (in .../lc3.css.less)
It only tells me the filename where the error is but no indication as to what line the error occurs on
What I'm currently doing is running $lessc app/assets/stylesheets/lc3.css.less
which tells me the line there's a "parse error" on.
Seems like an inefficient way to do it though, was wondering if anyone could share their process[detailed :O] for debugging LESS (and if they use source maps or something else to be able to edit live in browser)
The text was updated successfully, but these errors were encountered:
i can go line by line and always get this. i don't know what any error should mean. i wasted already 1 hour on my livestream with this and my viewers find it hilarious to see that i'm not capable of including a 3rd party library. i blame semantic-ui for it tho.
if there would be a solid error message, life would be easier
Sorry if this is not appropriate to be marked as an issue. I thought this may be an appropriate place as I'm specifically wondering about debugging LESS when using less-rails(.css.less files).
How do you debug errors in your .css.less file?
If I simply forget a semicolon in the file, when I load the file in the browser, I get
Less:Error at /Unrecognised input (in .../lc3.css.less)
It only tells me the filename where the error is but no indication as to what line the error occurs on
What I'm currently doing is running $lessc app/assets/stylesheets/lc3.css.less
which tells me the line there's a "parse error" on.
Seems like an inefficient way to do it though, was wondering if anyone could share their process[detailed :O] for debugging LESS (and if they use source maps or something else to be able to edit live in browser)
The text was updated successfully, but these errors were encountered: