freeCodeCamp/meet-the-node-console.english.md at d69c0592ec762978bd33ba34cee45a4deae2f324

Files

Jefferson Oliveira 6921c3fecc updates text for the location of the button (#37764 )

fixes the text describing the location of the logs button, due to the new design of the glitch.com website

2019-11-19 10:54:14 -06:00

1.8 KiB

Raw Blame History

id, title, challengeType, forumTopicId

id	title	challengeType	forumTopicId
587d7fb0367417b2b2512bed	Meet the Node console	2	301515

Description

During the development process, it is important to be able to check what’s going on in your code. Node is just a JavaScript environment. Like client side JavaScript, you can use the console to display useful debug information. On your local machine, you would see the console output in a terminal. On Glitch you can open the logs in the lower part of the screen. You can toggle the log panel with the button ‘Logs’ (lower-left, inside the tools menu). We recommend to keep the log panel open while working at these challenges. By reading the logs, you can be aware of the nature of errors that may occur.

Instructions

If you have not already done so, please read the instructions in the introduction and start a new project on Glitch using this link.

Modify the myApp.js file to log "Hello World" to the console.

Tests

tests:
  - text: <code>"Hello World"</code> should be in the console
    testString: 'getUserInput => $.get(getUserInput(''url'') + ''/_api/hello-console'').then(data => { assert.isTrue(data.passed, ''"Hello World" is not in the server console''); }, xhr => { throw new Error(xhr.responseText); })'

Challenge Seed

Solution

/**
  Backend challenges don't need solutions, 
  because they would need to be tested against a full working project. 
  Please check our contributing guidelines to learn more.
*/

1.8 KiB Raw Blame History Unescape Escape