Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialKilleon Patterson
18,528 PointsDifficulty starting npm
I'm having trouble starting npm in my project folder. I had the project open in its file with everything running fine, and then my computer had to restart. Now when I attempt to run npm start I receive error messages. I ran npm trace in the console and it told me to "specify configs in the ini-formatted file: C:\ Users/Leimamo/npmrc." I'm unsure of what configurations that the system is requesting.
Here is a link to my gist. https://gist.github.com/Satellite9/5e4ce3de5c19cee2f355d872b6d7d3c8
Thank you for your time.
Killeon
1 Answer
Andrew Chalkley
Treehouse Guest TeacherI'm unsure what the problem is. npmrc
is something related to npm
. Maybe uninstall and reinstall node.js and npm.
Killeon Patterson
18,528 PointsKilleon Patterson
18,528 PointsHello Andrew,
I was tinkering with solving the issue I was experiencing last night. I ran npm in the project folder, where it was reinstalled, and received these errors. One of them suggested that I did not have the correct versions of node and npm. Although, I didn't manual update either and they are not set for automatic updating. Do you recognize any of these errors as possible indicators to my issue? Thank you for your time.
Andrew Chalkley
Treehouse Guest TeacherAndrew Chalkley
Treehouse Guest TeacherIt looks like you haven't implemented an error handler for the mongo connection. It says the connection was refused...this could mean mongo isn't running, or the permissions aren't set up correctly.