Skip to content

Target's 'compile' not working (maybe meant to be so) #52

@justin-calleja

Description

@justin-calleja

Hi,

I'm not sure if this is intended or not. I am looking at the "Usage examples" (and what yo generates) and I tried configuring different targets for the jst task as follows but with the commented parts uncommented:

    jst: {
        options: {
            amd: true
        },
        build: {
            // compile: {
            files: {
                '.tmp/scripts/templates.js': ['<%= yeoman.app %>/scripts/templates/*.ejs']
            }
            // }
        },
        dev: {
            // compile: {
            files: {
                'app/scripts/templates.js': ['<%= yeoman.app %>/scripts/templates/*.ejs']
            }
            // }
        }
    },

With the 'compile' keys commented out it works. But the configuration for the default target uses 'compile'. Is this intentional? Perhaps my inexperience with Grunt is the problem.

Regards,
Justin

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions