Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

JavaScript Node.js Basics Handling Errors in Node The error event in Node

Tyler McDonald
Tyler McDonald
Full Stack JavaScript Techdegree Student 9,832 Points

Node not showing error with incorrect URL

Hello, I am following along with Reggie, but whenever I mistype the URL to force node to throw the error, it doesn't work. After about 30 seconds it throws an error connect ETIMEDOUT.

Is there a reason I am unable to get the same error as Reggie?

Here's my code:

const https = require("https");

function getProfile(username) {
  // Connect to the API URL
  const request = https.get(
    (response) => {
      let body = "";
      // Read the data
      response.on("data", (data) => (body += data.toString()));
      // Parse the data
      response.on("end", () => {
        const profile = JSON.parse(body);
  request.on("error", (error) => console.error(error));

// Print the data
function printMessage(profile) {
  const message = `${profile.name} (${profile.profile_name}) has ${profile.badges.length} total badge(s) and ${profile.points.total} points.`;

const users = process.argv.slice(2);

1 Answer

Steven Parker
Steven Parker
216,810 Points

The type of error you get depends on which part of the URL is incorrect:

If the URL points to a server that doesn't exist, a timeout is the type of error you should get (eventually).

On the other hand, if the URL points to a legitimate server, but to a resource that the server doesn't have, you'll get a "not found" error right away.