grunt-wiredep-copy's Introduction

grunt-wiredep-copy

Copies dependencies managed by wiredep

Getting Started

This plugin requires Grunt.

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-wiredep-copy --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-wiredep-copy');

The "wiredepCopy" task

Overview

In your project's Gruntfile, add a section named wiredepCopy to the data object passed into grunt.initConfig().

grunt.initConfig({
  wiredepCopy: {
    target: {
      options: {
        src: 'app',
        dest: 'dest',
        wiredep: {}
      }
    },
  },
})

Options

options.src

Type: String Default value: .

The directory containing the wiredep target.

options.dest

Type: String Default value: .

The destination directory to copy Bower dependencies to.

options.wiredep

Type: Object Default value: {}

Options passed through to wiredep.

Usage examples

Yeoman scaffolded project

wiredepCopy: {
  target: {
    options: {
      src: '<%= yeoman.app %>',
      dest: '<%= yeoman.dist %>',
      wiredep: '<%= wiredep.target %>'
    }
  }
}

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

License

grunt-wiredep-copy's People

Contributors

Stargazers

Watchers

grunt-wiredep-copy's Issues

Choosing files to copy

Hi,
is there a reason you're skipping 'packages', and instead going for the files chosen by wiredep (like 'js': [], 'css': [], etc.). The reason I'm asking is that wiredep ignores things like font files, even if they are listed in main, because it doesn't embed them into any file, or at least not that I managed to make it work. But if I just read all the main arrays from the packages object it works and all the dependencies are copied. It also works with overrides. Is there a gotcha that I'm not aware of?

wiredepCopy cdoesn't copy to the right place

I tried this tool because grunt-bower-task doesn't work as good as it should be with grunt-wiredep. I thought this task would do the job but it has a huge problem. It doesn't actually create the new file in the target location but keep renaming the file itself.

This is the block I have in my Gruntfile.js

wiredepCopy: {
      target: {
        options: {
          dest: 'app',
          wiredep: {
            task: {
              src: [
                'www/**/*.html',
                'www/css/**/*.css'
              ],
              options: {
              }
            }
          }
        }
      },
    }

when I type grunt wiredepCopy it creates a new file in app/ but it crates a new file in the same directory of the source renaming it to whateverappjs. Basically it replaces the dot at the beginning of the extension with the src.

Ideas? Any help would be much appreciated :)

Recommend Projects

tlvince / grunt-wiredep-copy Goto Github PK