Unable to disable sourcemap generation when specify option is used

[dw72]

When I use specify option to exclude some sass files from processing, then sourcemaps are always generated. I try to specify sourcemap: false option and sourcemap=false in config.rb without effect.

When I remove specify option sporcemaps works as expected.

[valer-cara]

+1

[peschee]

I'm experiencing the same issue. Is there a related issue or maybe a quick fix?

[maciej-gurban]

+1

This issue has been up for quite a while, without any resolution in sight. If you don't have enough time to look into it, please provide any pointers about where the issue could be. Thanks.

[maciej-gurban]

Here's the config I used while trying to output a CSS file without generating source map linked to it. As it is, sourcemap option will be ignored.

compass: {
    prod: {
        options: {
            sassDir: ['src/stylesheets'],
            cssDir:  ['src'],
            sourcemap: false
        }
    }
}

Method 1 Just add environment: 'production' to your options. This will also minify your CSS. If you want no sourcemap, but also your CSS unminified, see Method 2.

Method 2 In order for these options to execute, you need to run compass with --force parameter. As a temporary solution, open up file under node_modules/grunt-contrib-compass/tasks/compass.js in your project's directory, and find line containing compile(args, function () {

Then, create a new line just before it, and paste: args.push('--force');

And, that's about it. Now run your grunt task and enjoy.

The problem with this solution is, that while manually changing your local compass file works, all the changes will be wiped out after on npm update. Furthermore, it also makes it difficult to set up deployment scripts on external servers, since that would require either manually editing their files, and locking up compass versions, or creating a grunt task executing compass from command-line.

[peschee]

@vladikoff Has this issue been solved? Do you have a commit reference?