-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Source maps for CSS? #369
Comments
I'm definitely pro-explaining more about what's where. We had a request previously to include an unminified version of style.css in addition to the minified version so that might be a good place to start, but having more documentation here would also help |
If we're building the source map files, should they be included in the repo, or should they be in
The solution until then is to have the Gruntfile compile an all-in-one .less file and then rander source maps from that. |
It looks like gruntjs/grunt-contrib-less#243 isn't going to be merged in. (Unless a contributor reopens; they appear to be divided on the subject.) We can try this workaround or figure out something using grunt-contrib-concat. |
I've created a sourcemaps branch. f6b0daf puts sourcemaps inline, when Advantages of this over separate map files:
Disadvantages:
|
#646 merged, so closing this! |
Largo's CSS rules are scattered across a large number of LESS files, and sometimes tracking down which file is creating a property is difficult. It would be nice to have
grunt watch
orgrunt less
build source maps, even if they aren't included in this repository and are.gitignore
'd.Not something for 0.4, but something I think should be considered for future builds.
The text was updated successfully, but these errors were encountered: