-
Notifications
You must be signed in to change notification settings - Fork 0
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
[config - gu] Fix npm_global error when no globals #9
Labels
good first issue
Good for newcomers
Comments
I’m no longer seeing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An update to npm results in the global
node_modules
folder being deleted, so the command to get the list of packages fails (and doesn't record anything).If the folder does not exist (but npm does exist), we should assume that there are no global node packages and simply return "empty".
The text was updated successfully, but these errors were encountered: