Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
justin-calleja opened this issue Sep 6, 2014 · 0 comments
Open

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

justin-calleja opened this issue Sep 6, 2014 · 0 comments

Comments

@justin-calleja
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant