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
Hi, it seems the current version of setup.sh does not generate an up-to-date node.js version on a fresh EC2 Ubuntu micro instance. Unsure why, but upon completion 'node --version' will yield v0.6.12. This hinders loading jshint (which fails during to version mismatch) as well as additional node modules such as express. Perhaps the following sequence (taken from the course lecture) should be incorporated in setup.sh:
Seems to work for me. Did you try logging out and logging back in? Some of the profile changes don't fully apply until then (yes, you can also source config files, but we'd ideally need to engineer them to be idempotent). Try booting up a new instance and running these commands:
Hi, it seems the current version of setup.sh does not generate an up-to-date node.js version on a fresh EC2 Ubuntu micro instance. Unsure why, but upon completion 'node --version' will yield v0.6.12. This hinders loading jshint (which fails during to version mismatch) as well as additional node modules such as express. Perhaps the following sequence (taken from the course lecture) should be incorporated in setup.sh:
!/bin/sh
sudo apt-get update
sudo apt-get install -y python-software-properties python g++ make
sudo add-apt-repository -y ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install -y nodejs
The text was updated successfully, but these errors were encountered: