Hi, good to see someone else interested in this! It is workable but it's messy and it's not a workflow, more a worktrickle.
First up you to check that you have these versions of sass and compass running on your machine: mac:~ mac$ sass -v Sass 3.3.0.rc.2 (Maptastic Maple) mac:~ mac$ compass -v Compass 1.0.0.alpha.17 Now go the root of your project and do the following: mac:angular-seed-master mac$ sudo sass --compass --sourcemap --watch app/sass/styles.scss:app/css/styles.css Change the file directory/file names/locations as appropriate, if you are using the grunt twbs with sass and compass then you need to point to styles/main.scss:.tmp/styles/main.css You will see a sourcemap file created adjacent to your css file. Use chrome dev tools and have fun/be amazed. If you run grunt serve concurrently your fun won't last though. Grunt will try to write to the .tmp file, compile your sass and throw errors. The workaround is to --f (force) your way through grunt serve, discover and comment out the parts of your Gruntfile .js that are being performed by the above command line and try again. You might end up running sudo grunt serve because grunt will lose the permissions to write to the .tmp file. You can fix this by deleting the .sass cache files. I did all this as a shabby way to try and write a workable Gruntfile incorporating the sourcemap flag (see my original post). Someone could do this but not me, i don't have the smarts. Another way round this is not to use grunt serve but just run a local host and then run the command line sass stuff. Not ideal because you are losing most of the point of the workflow benefits. In summary what's needed is a correctly written Gruntfile that adds the sourcemap option and produces a sourcemap that is pointing to the right files. I think that the reason why just adding the sourcemap flag to the existing configuration isn't working is because the souremap that is created is using a different set of instructions and paths to the one that actually compiles from main.scss to main.css. @import 'app/bower_components/sass-bootstrap/lib/bootstrap'; This might explain why we are all succesfully creating useless souremaps. If this is complete nonsense well at least i'm trying! -----------------PS-------------------------------- Ref Duncan's question on the build errors you do need to uninstall all of your compass and sass gems. Bear in mind too that the order of this is important: sudo uninstall compass sudo uninstall sass sudo install compass -pre sudo uninstall sass sudo install sass --pre You can check your versions at any stage in this just to make sure that you are on the right track. Bear in mind that compass will install sass and overwrite your existing version hence the ordering above. Some of the above is OTT and i am sure that there is a simpler way. On Tuesday, February 4, 2014 2:51:22 PM UTC, Stephen Friedrich wrote: > > I, too had compiler errors after upgrading sass to the pre-release version. > However after updating both compass itself (to > 1.0.0.alpha.17<http://rubygems.org/gems/compass/versions/1.0.0.alpha.17>) > and grunt-contrib-compass (to 0.7.1) "grunt serve" works fine. > > Sadly, I now have the same problem: Line number are completely wrong - and > on first sight I think even files itself are not always accurate. > > On Tuesday, February 4, 2014 6:30:57 AM UTC+1, Duncan McDowell wrote: >> >> I won't be able to answer your question, but I'm interested to know how >> you got the pre-release sass version working with yeoman. Every time I try >> to upgrade, I get build errors when running grunt serve. >> > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
