-
-
Notifications
You must be signed in to change notification settings - Fork 252
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_config_prefix default shouldn't be a relative path #29
Comments
@louim yeah I agree that's a saner default for this role. I was using the context of a VM provisioned with a single non admin user whereas this role can be used elsewhere in a multi user environment. Just need to override this variable in the default config of Drupal VM to avoid introducing a regression geerlingguy/drupal-vm#629 |
I was just trying to get something similar working, with the latest version of Drupal VM. Here's the config I was trying to use in the config.yml:
I have also tried it without that last variable, and with the alternate option of The install for global packages just keeps failing. I will try to attach npm-debug.log as well, if that will be of any use. |
@sarahjean are you sure you are running the latest version of the role? The log make it look like it is trying to write to |
Not the latest, do I need to be on 3.1.0 for this? The latest tagged version of drupal-vm is running this
|
Yep: 3.0.0...3.1.0 |
@lulm, Ok, bumped the version and it worked beautifully. |
Fixed via #31 |
This will be in |
Hello!
#28 added a default
npm_config_prefix
of~/.npm-global
, and this path is added to the global path (for all users). So for all other user except theansible_ssh_user
, this path will not resolve because it will be expanded as their home folder.I think a better default would be something like:
/usr/local/lib/npm
, so the path will resolve for all users.What do you think?
cc @thom8
The text was updated successfully, but these errors were encountered: