/forkify

Food recipe app

Primary LanguageJavaScript

forkify

Food recipe app

Forkify App

πŸš€ Quick start

  1. Create a food recipe app.

    Use the npm install to get the dependencies ready.

  2. Start developing.

    Navigate into site’s directory and start it up.

    cd forkify/
    npm run start
  3. Open the source code and start editing!

    Your site is now running at http://localhost:8080!

🧐 What's inside?

A quick look at the top-level files and directories you'll see in this project.

.
β”œβ”€β”€ node_modules
β”œβ”€β”€ src
β”œβ”€β”€ .gitignore
β”œβ”€β”€ .prettierrc
β”œβ”€β”€ .babelrc
|--- webpack.config.js
β”œβ”€β”€ LICENSE
β”œβ”€β”€ package-lock.json
β”œβ”€β”€ package.json
└── README.md
  1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

  2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for β€œsource code”.

  3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

  4. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

  5. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

  6. README.md: A text file containing useful reference information about your project.

πŸŽ“ Learning Js