Skip to content
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

NPN Packages Global install on centos #57

Closed
jacinto123 opened this issue Nov 18, 2013 · 5 comments
Closed

NPN Packages Global install on centos #57

jacinto123 opened this issue Nov 18, 2013 · 5 comments

Comments

@jacinto123
Copy link

I have copied a pasted the code from the readme file:

package { 'express':
ensure => present,
provider => 'npm',
}

and I keep getting the following error:
Error: /Stage[main]//Package[express]: Provider npm is not functional on this host

It appears to install on the machine because when I get in I can do npm install or npm -v

I am using:
Node: 0.10.22
Npm: 1.3.14
Centos 6.4

Any ideas of whats going on? Am I missing something that is not in the readme?

@troelsselch
Copy link

I'm getting the same error.

I think it's because the npm package isn't available in the CentOS repositories. However the project site states that it should work on RedHat, and CentOS is a derivative of RedHat.

Any help or input would be nice.

@troelsselch
Copy link

Okay, I was a bit too quick on the trigger there. I got the following to work. note the manage_repo flag.

  class { 'nodejs':
    manage_repo  => true
  }

  package { 'jshint':
    provider => 'npm'
  }

@jacinto123
Copy link
Author

I get the following error when I try this:

Error: Invalid parameter manage_repo at /tmp/vagrant-puppet/manifests/base.pp:

@Twipped
Copy link

Twipped commented Dec 15, 2013

Also experiencing this problem, just started in the last week or two. I'm running both EPEL and REMI package sources, so npm is definitely available, and it does successfully install:

Notice: /Stage[main]/Nodejs/Package[nodejs]/ensure: created
Notice: /Stage[main]/Nodejs/Package[npm]/ensure: created

If I re-run the provisioning then the npm modules install fine, so this might be an order of operations issue.

@juniorsysadmin
Copy link
Member

Whatever the problem was, it should no longer be occurring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants