Closed y3g0r closed 5 years ago
Workaround: feed in some dummy task placeholder, like so:
$ gulp gulp --tasks
@y3g0r I reproduced by following the above steps, and I found that the 'unknown option' error was output by not gulp-cli
but commandar
in the gulpfile.js
. Please review the usage of commander
.
Thanks a lot for looking into it. I'll report the problem with commander
to hypothesis maintainers.
Problem
Running
gulp
with flag (except for--version
,--help
) w/o specifying a task returnserror: unknown option '<flag>'
, e.g.:Expected behavior
Running
gulp
with options fromgulp --help
should produce documented result.task
command line option shouldn't be always required.Steps to reproduce
I'm including project so that you can check if something is wrong with its
gulpfile.js
.$HOME
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.0/install.sh | zsh; exec $SHELL
nvm install 12.13.0
npm install --global gulp-cli
git clone https://github.com/hypothesis/client.git; cd client; git checkout 380f6de3
npm install
gulp --tasks
Environment
OS:
Node, npm & npx:
Gulp & gulp-cli:
Project:
P.S. I might be doing something stupidly wrong, I'm new to JS ecosystem, so don't get too mad.