/usr/bin/npm doesn't exist when setting a nodejs::npm::global_config_entry about puppet-nodejs HOT 10 CLOSED

Not sure that it makes a difference, but I've also had the nodejs class like this:

class { '::nodejs': }->

and had the same results

from puppet-nodejs.

AFAIK, you can't have a require relationship on a define.

However, it does seem like we should add an include ::nodejs to that define.

from puppet-nodejs.

Maybe split into two subclasses and contain them. Then order the two,
Class[a] -> Class [b]. You could try the spaceship collector but it's
possible a resource in the class will be out orpf order, unless you contain
the whole thing.

Rob Nelson
[email protected]

from puppet-nodejs.

@dandunckelman Is this still an issue with the latest release?

from puppet-nodejs.

@juniorsysadmin yes. On a 2nd puppet run, it is resolved...so it's not a deal breaker

from puppet-nodejs.

Tagging @ghoneycutt as this looks like the problem that #221 was supposed to solve.

from puppet-nodejs.

You shouldn't need the arrow syntax. The define will include the nodejs class. You are mixing include ::nodejs which happens in the define with the parameterized class syntax. Perhaps that is causing you trouble.

from puppet-nodejs.

I've since updated my class to this:

class ta_linux::ta_nodejs(
  $npm_packages = {},
) {
  validate_hash($npm_packages)

  $npm_package_defaults = {
    'provider' => 'npm',
    'require'  => Class['nodejs'],
  }

  class { 'nodejs': }

  nodejs::npm::global_config_entry { 'strict-ssl':
    ensure => present,
    value  => false,
  }

  Class['::nodejs'] -> Package <| provider == 'npm' |>

  create_resources(package, $npm_packages, $npm_package_defaults)
}

and still receive the error on the first run when the ta_linux::ta_nodejs class is loaded by another class like this:

class ta_apps::portal_web() {
  # other stuff to install packages, rvm, apache, and other stuff

  class { 'ta_linux::ta_nodejs':
    npm_packages => {
      'forever' => {
        'ensure' => hiera("pkg_ensure_forever"),
      },
    },
  }
}

from puppet-nodejs.

Can anyone else report that this is still occurring?

from puppet-nodejs.

Closing due to no further reports providing confirmation of a bug.

from puppet-nodejs.