You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
Before the change to use os-homedir, osenv.home() would return undefined in cases where HOME is not set.
After the change, home() throws an exception if it can't find a suitable home directory. This in turn means that importing the npm module at all fails, since it calls home() during startup.
This breaks things in environments like stripped-down containers where there is no home directory.
(I realize this change was made a long time ago, but a dependency of mine recently updated what version of the npm library it uses, suddenly causing these crashes.)
For now I am setting a dummy HOME in my environment, but this could have other side effects, so gracefully handling the lack of a home directory would be preferable.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before the change to use os-homedir,
osenv.home()
would returnundefined
in cases whereHOME
is not set.After the change,
home()
throws an exception if it can't find a suitable home directory. This in turn means that importing thenpm
module at all fails, since it callshome()
during startup.This breaks things in environments like stripped-down containers where there is no home directory.
(I realize this change was made a long time ago, but a dependency of mine recently updated what version of the
npm
library it uses, suddenly causing these crashes.)For now I am setting a dummy
HOME
in my environment, but this could have other side effects, so gracefully handling the lack of a home directory would be preferable.The text was updated successfully, but these errors were encountered: