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

bad option: --force on Node 10 #125

Closed
Uko opened this issue Oct 30, 2018 · 3 comments
Closed

bad option: --force on Node 10 #125

Uko opened this issue Oct 30, 2018 · 3 comments
Labels

Comments

@Uko
Copy link

Uko commented Oct 30, 2018

When I'm using grunt-cli (v1.3.1) with node 10 (doesn't happen on node 8 or node 9) like:

grunt taskname --verbose --force

I get an error stating:

node: bad option: --force

For some reason --force is not treated like a grunt command and it is propagated to node

@shama shama added the bug label Oct 30, 2018
@Arkni
Copy link
Member

Arkni commented Nov 4, 2018

This was fixed by #123.

@shama & @vladikoff could any of you, please, tag the current master and publish it to npm? (I can tag the release myself but I don't have npm permissions to publish)

Thanks :)

@vladikoff
Copy link
Member

@Arkni done 👍

@Uko
Copy link
Author

Uko commented Nov 4, 2018

Thanks all!

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

No branches or pull requests

4 participants