Bit further on with  this:

Firstly you can generate an accurate sourcemap with this:

// Compiles Sass to CSS and generates necessary files if requested
    compass: {
      options: {
        sourcemap: true,
        sassDir: '<%= yeoman.app %>/styles',

But you need to change the debug flag to false:

},
      server: {
        options: {
          debugInfo: false
        }
      }
    },

If you do this and now look at the generated css file i.e: 
.tmp/styles/main.css you will see commented out references that are 
entirely accurate, progress!

But you still cannot map to them in the elements panel because all of the 
bower_components/sass-bootstrap/lib 
in the dist are actually empty.

Some aspect of the grunt functionality is emptying these files, which makes 
sense in a dist because they are not needed, but without them no mapping is 
possible in production.

Any help appreciated!

P

On Thursday, January 30, 2014 12:49:36 AM UTC, P Stockton wrote:
>
> Hope that someone can point me  in the right direction, accept that this 
> may not be the right group for this but...
>
> I have a workflow set-up with  source maps in angular with comapss and 
> sass, so I know that i have the right versions of comapss and sass running.
>
>
> When I try to get it working with the useful Grunt Yo Angular scaffolding 
> (Compass/ TBS Sass options) I get sourcemaps created in .tmp/Styles and 
> everything appears to work as it should. The correct files are referenced 
> in the Elements panel but the line numbers are wrong.
>
> This is #153 of my gruntfile.js file, the only addition is highlighted:
>
> // Compiles Sass to CSS and generates necessary files if requested
>     compass: {
>       options: {
>         sourcemap: true,
>         sassDir: '<%= yeoman.app %>/styles',
>
> Any pointers would be welcome.
>
> P
>

-- 
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.

Reply via email to