• Home
  • Free Trial
  • Sign In
  • Techdegree
  • Tracks
  • Content Library
  • Community
  • Support
  • Jobs
    • Newest
      • Newest
      • Active
      • Unanswered
      • Featured
    • All Topics
      • All Topics
      • • General Discussion
      • • 21st Century Skills
      • • Android
      • • APIs
      • • Business
      • • C#
      • • Computer Science
      • • CSS
      • • Data Analysis
      • • Databases
      • • Design
      • • Development Tools
      • • Digital Literacy
      • • Equity, Diversity, and Inclusion (EDI)
      • • Go
      • • HTML
      • • Java
      • • JavaScript
      • • Learning Resources
      • • Machine Learning
      • • PHP
      • • Python
      • • Quality Assurance
      • • Ruby
      • • Security
  • James Barrett
    James Barrett
    13,253 Points

    Few questions for clarification

    Posted November 3, 2016 2:58pm by James Barrett
    James Barrett
    13,253 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Ilyes Medjedoub
    seal-mask
    .a{fill-rule:evenodd;}techdegree
    Ilyes Medjedoub
    Full Stack JavaScript Techdegree Student 1,238 Points

    Unexpected end of JSON input ERROR

    Posted October 8, 2016 4:14pm by Ilyes Medjedoub
    .a{fill-rule:evenodd;}techdegree
    Ilyes Medjedoub
    Full Stack JavaScript Techdegree Student 1,238 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Kathryn Notson
    Kathryn Notson
    25,941 Points

    Node.js Basics > Building a Command Line Application > Handling Parsing and Status Code Errors

    Posted October 6, 2016 6:00pm by Kathryn Notson
    Kathryn Notson
    25,941 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    0 Answers

  • ryanjones6
    ryanjones6
    13,797 Points

    Solution: statusCode not displaying short description

    Posted August 2, 2016 6:03pm by ryanjones6
    ryanjones6
    13,797 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    5 Answers

  • True Pixels
    True Pixels
    3,178 Points

    Not getting a response, no error message.

    Posted July 7, 2016 4:59am by True Pixels
    True Pixels
    3,178 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Bryan Woodard
    Bryan Woodard
    5,757 Points

    Why am I not getting the same result?

    Posted April 17, 2016 5:26am by Bryan Woodard
    Bryan Woodard
    5,757 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Alex Parker
    Alex Parker
    980 Points

    When we are handling a connection error, we dont pass arguments to printError. Why?

    Posted April 7, 2016 1:14am by Alex Parker
    Alex Parker
    980 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Maria Campbell
    Maria Campbell
    8,641 Points

    I got the wrong error when testing out printError in stage_2_video_6 with message object.

    Posted March 14, 2016 3:47pm by Maria Campbell
    Maria Campbell
    8,641 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Floyd Orr
    Floyd Orr
    11,723 Points

    Is this production code from node document or just example. I see there is no function is this a different style .

    Posted March 10, 2016 2:54pm by Floyd Orr
    Floyd Orr
    11,723 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • fngr
    fngr
    11,179 Points

    Another way to handle the statusCode error?

    Posted March 8, 2016 1:36pm by fngr
    fngr
    11,179 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    0 Answers

  • Developers UA
    PLUS
    Developers UA
    Courses Plus Student 39,426 Points

    Still showing up an error message

    Posted February 22, 2016 8:39am by Developers UA
    Developers UA
    Courses Plus Student 39,426 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Kevin Faust
    Kevin Faust
    15,353 Points

    node.js try-catch block placement question

    Posted February 11, 2016 2:56am by Kevin Faust
    Kevin Faust
    15,353 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Mike Ulvila
    Mike Ulvila
    16,268 Points

    Some serious confusion between require http and https for us beginners. Please consider an update to this tutorial.

    Posted January 21, 2016 8:19pm by Mike Ulvila
    Mike Ulvila
    16,268 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    4 Answers

  • cindy li
    cindy li
    1,057 Points

    Status code 301 for Node.js exercise

    Posted December 16, 2015 6:43pm by cindy li
    cindy li
    1,057 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Maksim Nesterenko
    Maksim Nesterenko
    1,387 Points

    I've got a TypeError instead of printing out message to the console

    Posted November 22, 2015 6:30pm by Maksim Nesterenko
    Maksim Nesterenko
    1,387 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Saad Khan Malik
    Saad Khan Malik
    25,199 Points

    Property error on "https.STATUS_CODES"

    Posted November 19, 2015 11:18pm by Saad Khan Malik
    Saad Khan Malik
    25,199 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    0 Answers

  • Saad Khan Malik
    Saad Khan Malik
    25,199 Points

    Property error on "https.STATUS_CODES"

    Posted November 19, 2015 11:18pm by Saad Khan Malik
    Saad Khan Malik
    25,199 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    3 Answers

  • Brendan Whiting
    seal-mask
    .a{fill-rule:evenodd;}techdegree seal-36
    Brendan Whiting
    Front End Web Development Techdegree Graduate 84,697 Points

    I get "Unexpected token ILLEGAL" instead of "Unexpected token N", and also a whole lot longer string in response.

    Posted October 30, 2015 12:37am by Brendan Whiting
    .a{fill-rule:evenodd;}techdegree seal-36
    Brendan Whiting
    Front End Web Development Techdegree Graduate 84,697 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    0 Answers

  • Nicholas Palenchar
    Nicholas Palenchar
    784 Points

    http.STATUS_CODES no longer applicable

    Posted October 21, 2015 7:03pm by Nicholas Palenchar
    Nicholas Palenchar
    784 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    7 Answers

  • Unsubscribed User
    Unsubscribed User
    8,841 Points

    Error Message 'connect ECONNREFUSED' - Resolved

    Posted October 13, 2015 4:19am by Unsubscribed User
    Unsubscribed User
    8,841 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • zachstockmal
    zachstockmal
    6,413 Points

    Why is my console printing "There was an error getting the profile for chalker123. ([object Object])"

    Posted September 3, 2015 6:57pm by zachstockmal
    zachstockmal
    6,413 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • James Kim
    James Kim
    8,475 Points

    Why do you need Try and Catch method?

    Posted August 11, 2015 7:14pm by James Kim
    James Kim
    8,475 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • maximshmatko
    maximshmatko
    21,170 Points

    Just to let you guys know, there currently IS a user with the name "chalkers123". =]

    Posted June 16, 2015 2:14pm by maximshmatko
    maximshmatko
    21,170 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    0 Answers

  • Aaron Hill
    Aaron Hill
    9,732 Points

    Getting TypeError when trying to create status code errors.

    Posted June 16, 2015 1:06am by Aaron Hill
    Aaron Hill
    9,732 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    5 Answers

  • Jamie McDonald
    Jamie McDonald
    5,632 Points

    Where/when is the get request sent in this Node.js basics program?

    Posted May 29, 2015 12:42pm by Jamie McDonald
    Jamie McDonald
    5,632 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Nils Eriksson
    Nils Eriksson
    3,396 Points

    We don't call printError with a parameter, how does that work ?

    Posted March 27, 2015 3:49pm by Nils Eriksson
    Nils Eriksson
    3,396 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

  • Mauro Javier Aguirre Sanroman
    Mauro Javier Aguirre Sanroman
    11,510 Points

    Where can i learn more about node.js?

    Posted March 20, 2015 8:48am by Mauro Javier Aguirre Sanroman
    Mauro Javier Aguirre Sanroman
    11,510 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Fareez Ahmed
    Fareez Ahmed
    12,728 Points

    There was an error getting the profile for chalkers. (OK)

    Posted February 20, 2015 5:51pm by Fareez Ahmed
    Fareez Ahmed
    12,728 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    2 Answers

  • Anish Walawalkar
    Anish Walawalkar
    8,534 Points

    Why are the response.on methods not inside the if(response.statusCode == 200) {} statement?

    Posted December 17, 2014 3:44am by Anish Walawalkar
    Anish Walawalkar
    8,534 Points
    • JavaScript
    • Node.js Basics (2014)
    • Building a Command Line Application
    • Handling Parsing and Status Code Errors

    1 Answer

Posting to the forum is only allowed for members with active accounts.
Please sign in or sign up to post.

    Treehouse

  • About
  • Blog
  • Careers
  • Community
  • Stories
  • Shop
  • Contact
  • Gift Card

See Full Catalogue

Techdegree

  • Front End Web Development
  • Full Stack JavaScript
  • Python Development
  • Data Analysis
  • UX Design

Tracks

  • Learn to Code for Beginners
  • Beginning Python
  • Beginning SQL
  • Beginning Java
  • ...see more

Courses

  • JavaScript Basics
  • Intro to HTML & CSS
  • Python Basics
  • CSS Layout
  • ...see more

Explore

  • Perks
  • Treehouse for Libraries
  • Treehouse for Teams
  • Twitter
  • YouTube
  • Facebook
  • LinkedIn
  • Instagram
Terms & Conditions | Privacy

© 2022 Treehouse Island, Inc.