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.

Sign up for GitHub

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

Jump to bottom

Can't have command-line argument "--module" in Node 12 #132

Open

cakoose opened this issue Dec 13, 2019 · 1 comment

Labels

cakoose commented Dec 13, 2019

Some of my Grunt tasks take a "--module=..." argument. Under Node 8.15.0, things work fine:

$ grunt --hello=asdf 
Warning: Task "default" not found. Use --force to continue.

Aborted due to warnings.
$ grunt --module=asdf
Warning: Task "default" not found. Use --force to continue.

Under Node 10 and above, something goes wrong when I use "--module=...".

$ grunt --hello=asdf  
Warning: Task "default" not found. Use --force to continue.

Aborted due to warnings.
$ grunt --module=asdf
/Users/kannan/.nodenv/versions/10.17.0/bin/node: bad option: --module=asdf

The text was updated successfully, but these errors were encountered:

sateffen commented Mar 1, 2020

The problem can't be solved by grunt I guess, as --module is an option in node itself.

--module execute a file as a JavaScript module.
Note: the --module option is implicitly enabled for *.mjs files.

Krinkle added the question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment