In this lab, you will be building a recipe CRUD app using Express as a web server and a local JSON file as a back end.

Students should get hands-on experience with:

• Express.js
• Using Node's fs module to read and write to a file
• Using JSON.parse and JSON.stringify to convert between JSON and JavaScript objects

Students should start internalizing the concepts of:

• URL "end points" as a shortcut for a resource
• listening for HTTP requests
• sending HTTP responses

You will have some recipes to start with in data/recipea-data.json. You will have to create a JavaScript file in the src directory to be your program.

You will know you're successful when you can run your JS file, and then, while the server is running, make requests to the URLs in your specifications and get the response you expect.

You will run the code in your src directory by navigating into that directory and running node [file name]. For example, if you name your file recipe-program.js, you would run node recipe-program.js in the src directory.

• You can alternately run node --watch [file name] to re-run the server every time changes are saved to the file or any file in its directory.

The data in recipea-data.json is an array of recipes. Each recipe is an object with the following properties:

• name - the name of the recipe
• cookingMethod - the cooking method of the recipe
• ingredients - an array of ingredients

Check out the data in data/recipea-data.json to see what that looks like.

There is also a backup of this file. You will find it in data/backup-recipea-data.json. This is because it is very easy to write code that deletes or mangles your data. Always have a backup!

Your API should have the following features:

When the app receives an HTTP request for all recipes, it reads from the data file and returns all recipes in JSON format.

http://localhost:3000/find-recipes

[
  {
    "name": "Spaghetti with White Sauce",
    "cookingMethod": "stove-top boil",
    "ingredients": [
      "spaghetti",
      "butter",
      "flour",
      "milk",
      "salt",
      "pepper",
      "garlic",
      "parmesan cheese"
    ]
  },
  {
    "name": "Spaghetti with Red Sauce",
    "cookingMethod": "stove-top boil",
    "ingredients": [
      "spaghetti",
      "tomato sauce",
      "tomato paste",
      "ground beef",
      "salt",
      "pepper",
      "garlic",
      "onion",
      "parmesan cheese"
    ]
  },
  {
    "name": "Fried Chicken",
    "cookingMethod": "deep fry",
    "ingredients": ["chicken", "flour", "salt", "pepper", "garlic", "oil"]
  },
  {
    "name": "Baked Chicken",
    "cookingMethod": "oven bake",
    "ingredients": ["chicken", "salt", "pepper", "garlic", "oil"]
  }
]

When the app receives an HTTP request for a specific recipe, it reads from the data file and returns that recipe in JSON format.

http://locahost:3000/find-recipe/1

{
  "name": "Spaghetti with Red Sauce",
  "cookingMethod": "stove-top boil",
  "ingredients": [
    "spaghetti",
    "tomato sauce",
    "tomato paste",
    "ground beef",
    "salt",
    "pepper",
    "garlic",
    "onion",
    "parmesan cheese"
  ]
}

When the app receives an HTTP request to delete a specific recipe, it deletes that recipe from the data file and returns an HTTP message indicating it's done so.

http://localhost:3000/trash-recipea/1

You can decide how to indicate that the recipe has been deleted. One method is to simply send back a string with a message that it's been deleted. Another, more common method is to send back the data that was deleted.

The way to check that you have achieved this one is to look at the data file itself and see if the recipe at that index has been removed.

Feel free to copy the backup file's contents back to the /data/recipea-data.json file after testing this feature!

Your instructor will share with you the final result of your codealong.