Gscan Latest version not working

[mskian]

gscan latest package not working
when try to test end up with

gscan --fatal --verbose .
/usr/bin/env: invalid option -- 'S'
Try '/usr/bin/env --help' for more information.

gscan .
/usr/bin/env: invalid option -- 'S'
Try '/usr/bin/env --help' for more information.

Live-action - https://github.com/TryGhost/London/runs/576771741

issue on 3.5.1
3.4.0 works well

[naz]

Hey @mskian, could you please provide the information on the environment (OS, node version, etc.) you are running the command in?

[mskian]

OS: ubuntu 18.04 LTS
Node: v10.20.0
ghost: 3.13.1
Ghost-CLI version: 1.13.1

Just run the gscan CLI test in the theme folder

[mskian]

I think due to this - 7954aee

[mskian]

gscan/bin/cli.js

#!/usr/bin/env node
const prettyCLI = require('@tryghost/pretty-cli');
const ui = require('@tryghost/pretty-cli').ui;
const _ = require('lodash');
const chalk = require('chalk');
const gscan = require('../lib');

I tried this
this will work

[ErisDS]

@daniellockyer can you do a little bit more looking into this to see if there's another method to get rid of the warning, and if you can't find one in an hour or so lemme know?

Last resort I'll try to refactor the output so the warning doesn't look like part of the gscan output

[daniellockyer]

@ErisDS Can't find anything ☹️

https://www.xiaoru.li/post/disabling-node-warnings/ mentions the same issue and their recommendation:

If you only wanted to disable the warnings because you used the fs.promises API as I did, I would recommend you to wrap the original APIs in a promise manually next time to avoid the hassle, or simply sticking to util.promisify as well as the sync version of the APIs, instead of using this workaround.

[ErisDS]

Yeah - but we're not using the fs.promises API, a dependency 3 levels deep is :(

[ErisDS]

I've raised this as an issue against Node.js: nodejs/node#32876

We obviously need this working on ubuntu, I'll take a look to see if I can minimize the impact of the warning.

[markmssd]

Ran into the same issue, glad I wasn't crazy! I had to downgrade to 3.4.1 to have it work.

[ErisDS]

After a bit of a back-and-forth, we've found an OS-agnostic solution using process.removeAllListeners()

Fix and release incoming!

[markmssd]

Working with this fix, thank you @ErisDS !