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 trialRobert Ungar
15,723 PointsProject files are broken
I've downloaded the project files, navigated into the first folder and run npm install. After installing all of the packages and trying to run the server, it immediately crashes with the following message:
'(node:14908) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: "listener" argument must be a function (node:14908) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.'
Please update the project files.
Jere Green
1,029 PointsJere Green
1,029 PointsI tried the downloaded code and it ran fine. It runs but doesn't do the actual loading of images because that's what we'll fill in as we take the course.
You might start over with a clean directory and npm install.
It would help to specify more detail about what directory and files you were actually trying to run, since the zip file contains many projects and each seems to have an initial and final state.
I ran both gif-search and gif-search_final below: The screenshot is from gif-search (the incomplete starting project).
The gif-search_final didn't display any images for me but I noticed that it seemed to load data using the giphy API. In looking over the code for this final version, it doesn't seem to have any code to actually load the retrieved images into the React components. It just uses a console.log to show that it retrieved the data. It looks like later versions of the projects fill in these capabilities.
I'm running Node v8.2.1 and Chrome 60
I only have two eslint warnings as viewable in the console in the screenshot.
It looks like it hasn't been updated recently, so it doesn't appear that they fixed it in the short period since you asked the question.
It makes it much easier to read the technical details if they are formatted nicely. I'd recommend doing a google search like: Some links to pages about how to nicely format Treehouse Community posts.
An external search engine seems necessary because apparently the built-in Treehouse Community search really sucks.