2

ターミナル経由で gruntfile から登録済みのタスクを取得したいと思います。

例：

grunt.registerTask('test', ['clean', 'compass', 'uglify', 'cssmin', 'imagemin', 'copy:test', 'ftp-deploy:test', 'clean']);

次に、端末で次のように入力します

$> grunt --listtasks

次のような説明で各タスクを登録できればさらに良いでしょう:

grunt.registerTask('test', 'this task deploys to testserver',['clean', 'compass', 'uglify', 'cssmin', 'imagemin', 'copy:test', 'ftp-deploy:test', 'clean']);

次に、出力は次のようになります。

$> test: this task deploys to testserver (clean, compass, uglify, cssmin, imagemin, copy:test, ftp-deploy:test, clean)
4

2 に答える 2

1

またはgrunt-available-tasks を見てください:

出力例

于 2015-01-11T15:13:08.663 に答える
1

実行grunt --helpして、登録されているすべてのタスクのリストを取得します。コマンドとタスクの説明が表示されます。出力例:

$ grunt --help
Grunt: The JavaScript Task Runner (v0.4.1)

Usage
 grunt [options] [task [task ...]]

Options
         --help, -h  Display this help text.
             --base  Specify an alternate base path. By default, all file paths
                     are relative to the Gruntfile. (grunt.file.setBase) *
         --no-color  Disable colored output.
        --gruntfile  Specify an alternate Gruntfile. By default, grunt looks in
                     the current or parent directories for the nearest
                     Gruntfile.js or Gruntfile.coffee file.
        --debug, -d  Enable debugging mode for tasks that support it.
            --stack  Print a stack trace when exiting with a warning or fatal
                     error.
        --force, -f  A way to force your way past warnings. Want a suggestion?
                     Don't use this option, fix your code.
            --tasks  Additional directory paths to scan for task and "extra"
                     files. (grunt.loadTasks) *
              --npm  Npm-installed grunt plugins to scan for task and "extra"
                     files. (grunt.loadNpmTasks) *
         --no-write  Disable writing files (dry run).
      --verbose, -v  Verbose mode. A lot more information output.
      --version, -V  Print the grunt version. Combine with --verbose for more
                     info.
       --completion  Output shell auto-completion rules. See the grunt-cli
                     documentation for more information.

Options marked with * have methods exposed via the grunt API and should instead
be specified inside the Gruntfile wherever possible.

Available tasks
            rosetta  Shared variables between JS and CSS. *
            asciify  Ascii awesomizer. A Grunt task for better banners and hot
                     logs. *
              clear  Clear your terminal window
              clean  Clean files and folders. *
             concat  Concatenate files. *
             jshint  Validate files with JSHint. *
               sass  Compile Sass to CSS *
              watch  Run predefined tasks whenever watched files change.
               csso  Minify CSS files with CSSO. *
         lintspaces  Checking spaces *
              newer  Run a task with only those source files that have been
                     modified since the last successful run.
          any-newer  Run a task with all source files if any have been modified
                     since the last successful run.
    newer-timestamp  Internal task.
             svgmin  Minify SVG *
 trimtrailingspaces  Removing the trailing spaces *
            webfont  Compile separate SVG files to webfont *

Tasks run in the order specified. Arguments may be passed to tasks that accept
them by using colons, like "lint:files". Tasks marked with * are "multi tasks"
and will iterate over all sub-targets if no argument is specified.

The list of available tasks may change based on tasks directories or grunt
plugins specified in the Gruntfile or via command-line options.

For more information, see http://gruntjs.com/
于 2013-09-22T12:57:50.857 に答える