Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 20 07:29
    nareshabbanapuri commented #198
  • Jan 19 09:54
    nareshabbanapuri commented #198
  • Jan 19 09:38
    nareshabbanapuri commented #198
  • Jan 19 08:32
    nareshabbanapuri commented #198
  • Jan 19 08:31
    nareshabbanapuri opened #198
  • Jan 15 09:41
    mburns unassigned #2
  • Jan 07 14:36
    jeffbyrnes commented #195
  • Dec 21 2018 03:16
  • Dec 06 2018 02:27
    ronny-macmaster starred redguide/nodejs
  • Nov 29 2018 20:08
  • Nov 27 2018 04:27
    Munsen starred redguide/nodejs
  • Nov 15 2018 15:06
    edgamen starred redguide/nodejs
  • Nov 13 2018 17:00
  • Oct 31 2018 22:28
    twalker starred redguide/nodejs
  • Oct 26 2018 11:48
    mmarod closed #157
  • Oct 24 2018 15:16
    anhtuannguyentran starred redguide/nodejs
  • Oct 12 2018 16:00
    jeffbyrnes commented #195
  • Oct 12 2018 15:30
    jeffbyrnes synchronize #196
  • Oct 12 2018 15:26
    jeffbyrnes synchronize #195
  • Oct 11 2018 17:53

    tas50 on v6.0.0

    (compare)

Abdul Hagi
@ballerabdude
@NickHeiner you have to include the recipe that will install npm from source using this
"include_recipe 'nodejs::npm_from_source'"
then that recipe will download the npm using the new version you overwrite
Nick Heiner
@NickHeiner
@ballerabdude that worked – thanks!
Nick Couraud
@ncouraud
when running 'nodejs::iojs' on Ubuntu 14.04 it looks like it keeps installing Nodejs 0.10.40 - I tried installing binaries, but it looks like that will only install from nodejs.org/dist not iojs. Am I missing something?
Ramya Kailas
@ramyakailas
Hi
I am exploring the node.js cookbook and there is an nodejs_npm provider which accepts packages.json by default
How do i define my package.json
Ramya Kailas
@ramyakailas
Where can i store my package.json file for the recipe to pick it up
Ramya Kailas
@ramyakailas
Hi nodejs newbie question
Ramya Kailas
@ramyakailas
Hey Everybody , some of the packages in package.json point to a private git repo
i am getting a 404 for them
how do i handle this in the recipe
Guilhem Lettron
@guilhem
Hi @ramyakailas I don't know if you can manage this directly in package.json but it can't be in this cookbook. Maybe you can add some configuration in global git
Ramya Kailas
@ramyakailas
hi@guilhem , i copied my ssh keys to the vm , but still fighting with the private repo issue
Miguel Moll
@MiguelMoll
Hi all! Running into an interesting problem where npm packages aren't being installed because the they are skipped. Looks like it has detected the package as already installed. Thought it was related to this issue: redguide/nodejs#50
But doesn't seem to be related because there are zero users that have the package installed. Any tips?
Guilhem Lettron
@guilhem
@miguelmoll can you test with latest master?
I merged something who can help
Miguel Moll
@MiguelMoll
@guilhem Thanks! Will give it a shot in a bit.
Miguel Moll
@MiguelMoll
@guilhem Awesome! Looks like it worked with my initial testing. Thank you!
Curious would this fix make its way to chef supermarket anytime soon?
Guilhem Lettron
@guilhem
@miguelMoll yeah I will push a bugfix version
Miguel Moll
@MiguelMoll
Very cool. Thank you again for your help!
Guilhem Lettron
@guilhem
@MiguelMoll done ;)
Graham Weldon
@predominant
Hey folks.
Anyone notice the nodejs.org website is now redirecting all http:// traffic to https:// with 301?
If anyone has installed nodejs from package, and needs to do npm installs for things that require compilation (downlaoding nodejs source) then it fails as the URL is http://
Not sure what I can do about that.. but created a pull request for changing the download URL for the source install method.
Barthélemy Vessemont
@BarthV
hi
My dev team is also hitting https issue this morning
We probably need to fix some url headers somewhere
but I didn't have tested this so far
Graham Weldon
@predominant
redguide/nodejs#98
@BarthV : ^
Barthélemy Vessemont
@BarthV
ok
quite obvious fix
:)
merged
Graham Weldon
@predominant
That fixes basic install.
Packages referenced for package install have an issue though
Barthélemy Vessemont
@BarthV
bundle exec kitchen converge package-ubuntu-1404 is ok for me
vagrant@package-ubuntu-1404:~$ node -v
v0.10.40
vagrant@package-ubuntu-1404:~$ npm -v
1.4.28
vagrant@package-ubuntu-1404:~$ dpkg -l |egrep -i "node|npm"
ii  nodejs                              0.10.40-1nodesource1~trusty1     amd64        Node.js event-based server-side javascript engine
what is missing for you ? (on which platform ?)
Graham Weldon
@predominant
Oh, when you NPM install something with build dependencies.
Like iconv or something
The build requires download of the nodejs source, which references http://nodejs.org/dist/....
So the npm download of the source pulls down the result of the 301 redirect now in place on the site.
And fails install.
gyp verb ensuring nodedir is created /opt/mimo/node_modules/xml2json/node_modules/node-expat/node_modules/iconv/.node-gyp/0.10.40
gyp verb created nodedir /opt/mimo/node_modules/xml2json/node_modules/node-expat/node_modules/iconv/.node-gyp
gyp http GET http://nodejs.org/dist/v0.10.40/node-v0.10.40.tar.gz
gyp http 200 http://nodejs.org/dist/v0.10.40/node-v0.10.40.tar.gz
gyp WARN install got an error, rolling back install
gyp verb command remove [ '0.10.40' ]
...
Note the middle 2 http calls.