-
Notifications
You must be signed in to change notification settings - Fork 15
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
npm-consider fails on "Impact" #11
Comments
Edit: accidentally hit CTRL+ENTER while writing, then realised what I was typing didn't even matter anyway so I removed it. |
Just got the same error, it seems, on macOS. The following is what I tried exactly:
As this been fixed somehow? Or maybe someone has any clue on the problem, so I could try and help myself? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The issue is exactly as the title says:
npm-consider
seems to fail when selectingImpact
. Associated command output with stack trace is below (tested usingexpress
with commandnpm-consider install --save express
):Note that this error also occurs if I attempt to use the module directly in the Windows command prompt.
The text was updated successfully, but these errors were encountered: