grunt --tasks broken about grunt-cli HOT 8 CLOSED

The grunt --tasks option requires an additional argument, which is a directory path to scan for task files. See grunt --help for more information.

from grunt-cli.

I don't think this issue should be closed. The task should display an error message to the user rather than a stack trace. The stack trace isn't actionable to a user. Furthermore, in my opinion the documentation isn't clear about what the flag expects. Besides, why can't grunt --tasks use the current directory by default?

from grunt-cli.

The way the command line parser works is that because --tasks expects an additional argument, it will consume whatever follows it. Doing grunt mytask --tasks ./tasksdir will work the same as grunt --tasks ./tasksdir mytask. But they will behave totally differently if you omit the necessary argument after --tasks.

That being said, I'm all for better error messages. Can you open a ticket about improving error messages with misused command line options?

from grunt-cli.

(And reference this ticket, too)

from grunt-cli.

Ok. Thanks. Went through the same process.

Used to rake -T, run grunt --tasks and start googling.

from grunt-cli.

Uhhh. So, again, how do I list available tasks?..

Seeing a traceback is not particularly enlightening when a user wants to do something very simple.

from grunt-cli.

@ulidtko -- do grunt -h and you'll see the available tasks after all of the options you can pass.

from grunt-cli.

Thanks, @bisrael. That was what I was looking for too - didn't spot it first time around.

from grunt-cli.