Skip to content

tools-of-software-projects/calorie-tracker

Repository files navigation

Project Name

Calorie Counter

Description

We are working on a web-based service to track the amount of calories being consumed by the users over a selected period of time. Users will have their own accounts where they can save their consumption history. They can select a variety of food from a list and add it to their daily sum of calories. We plan to use cloud services and an API from a 3rd party service that has an extensive database of food selection.

Documentation

The documentation of the project can be accessed within the project folder, it's PDF file named Documentation.pdf

Available Scripts

In the project directory, you can run:

npm run launch

Installs all the modules and runs the app in the development mode.

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.