I don’t know @michaelba21. I can’t help you. I’ve played with Node before but I’m not that far yet in the fCC curriculum. So I tried doing the first step of Backend/API myself, both on my local system and in Gitpod. In both cases, “Hello World” was logged in the console, but when I shared the Gitpod link in this step, like you did, my test didn’t pass either. (BTW, if anyone wants to do this project on their local system, you need to run “npm install node_module” to get the node_modules folder.) Sorry.
I do not know answer of this question. anyone knows this??? Please if you know the answer reply to me. thanks.
Working on these challenges will involve you writing your code using one of the following methods:
Use a site builder of your choice to complete the project. Be sure to incorporate all the files from our GitHub repo.
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 console output in a terminal. On Gitpod, a terminal is open at the bottom of the editor by default.
We recommend to keep the terminal open while working at these challenges. By reading the output in the terminal, you can see any errors that may occur.
The server must be restarted after making changes to its files.
You can stop the server from the terminal using Ctrl + C and start it using Node directly (node mainEntryFile.js) or using a run script in the package.json file with npm run.
For example, the "start": "node server.js" script would be run from the terminal using npm run start.
To implement server auto restarting on file save Node provides the --watch flag you can add to your start script "start": "node --watch server.js" or you can install an npm package like nodemon. We will leave this to you as an exercise.
Modify the myApp.js file to log “Hello World” to the console.
