Add option to specify destination directory for taks about grunt-jade-usemin HOT 12 CLOSED

Did you try using the options targetPrefix ?

What Dest directory are you referring to? the one that the compiled css/js gets compiled to or the ones for the destination jade file?

from grunt-jade-usemin.

@pgilad Thanks for the help, options targetPrefix is that I need 👍

from grunt-jade-usemin.

It's seem I have found a bug when using options targetPrefix provided. On the following config:

    jadeUsemin: {
        vendor: {
            options: {
                tasks: {
                    js: ['concat', 'filerev'],
                    css: ['concat', 'filerev']
                },
                targetPrefix: '.tmp',
                dirTasks: 'filerev'
            },
            files: [{
                    expand: true,
                    cwd: "src/to/views",
                    src: ['*.jade'],
                    dest: 'build/views'
                }
            ]
        }
    }

Paths In the compiled views added without filerev hashes.

from grunt-jade-usemin.

Can you try running grunt jadeUsemin:vendor --verbose?

from grunt-jade-usemin.

@pgilad unfortunately I can't show my technical detail for all. Please could you try my config yourself?

from grunt-jade-usemin.

I could but I don't have your dir file structure and/or your files...
Also you are getting targetPrefix options wrong. Why do you want to output compiled files there?

How do you run your task?

from grunt-jade-usemin.

Why I'm using targetPrefix option wrong? A need to reside files to .tmp directory first because I use google closure compiler for my js files but it does't support destination directory as source one.

I run my task via Gruntfile.

from grunt-jade-usemin.

I'm going to need either a verbose log (run with grunt jadeUsemin --verbose) or access to the files, since I can't use your config without the files.

Perhaps try to create a minimum test case where the task fails so that this can be debugged.

The targetPrefix + filerev have been successfully used by others & me, and also have passing tests for them, so either it's an edge case that doesn't get handled right or you might be using it wrong

from grunt-jade-usemin.

Hi, I had the same error as @skotchio that paths in the compiled views had no filerev hashes.

The problem was caused by missing / at the end in prefix and targetPrefix. @pgilad you can try this by removing slash in Gruntfile.js: https://github.com/pgilad/grunt-jade-usemin/blob/master/Gruntfile.js#L69-L70 ... tests will fail.

from grunt-jade-usemin.

It's a problem with targetPrefix, when only prefix doesn't contain slash, tests pass.

from grunt-jade-usemin.

Hi, thanks for the discovery, can you create a failing PR test case for this (and a possible fix)?
I think we can easily make sure prefix contains an ending slash...

from grunt-jade-usemin.

Fixed and thanks to @ppitonak for the help...

from grunt-jade-usemin.