Simon Boudrias

Oh quite possible then, would you mind testing on the latest release?

FWIW, the repo contains beta versions of a fully reimplemented version of Inquirer without rxjs (see https://github.com/SBoudrias/Inquirer.js/issues/692) It's not complete, but most prompts are functional and deployed to npm already....

Of course, this is on the `master` branch, but in different section of the monorepo. Inside the [`packages/**` root](https://github.com/SBoudrias/Inquirer.js/tree/master/packages), every folder except `inquirer` are new prompts implemented without the rxjs...

Thanks, I believe we just don't handle the Promise failure in that way. When we moved from callbacks to promises, we only handled successful promise passing the status (true/false). Rejected...

Hey @pensierinmusica, which prompt are you using when this happens?

You can use the `--ignore-engines` when using yarn: https://yarnpkg.com/lang/en/docs/cli/install/#toc-yarn-install-ignore-engines I'm not sure how we can fix that on our side without removing functionality. Maybe we could leverage `optionalDependencies`, but then...

Could you open an issue on `global-tunnel-ng` about that problem: > Unfortunately global-tunnel-ng ignores the presence of NO_PROXY config. Sounds like we'd just want a fix on that package.

Probably good. :) I'd go further and throw and error and prevent the process from running.

I'm not sure, I think we just implemented an alert if there's a `.yo-rc.json` file in the user home dir.

Any chance your generator JS files are broken? When we search for generators, we don't actually require the JS files; but we do when trying to run one.