Skip to content

banurekhaMohan279/Hunger-Buddy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

React Restaurants App - Hunger Buddy

Built With API from Zomato Dev API

App At Work

Process Summary

Tech Stack:

  • React JS - Redux
  • Babel
  • Webpack
  • HTML
  • CSS

Features

  • Infinite load - Interaction Observer API

The Process

Setup

SSR vs SPA?
  • SSR with Next
  • SPA with React
React boilerplate?
  • With CRA
  • Without CRA
  • CRA-PWA
  • Without npm - very basic
Data storage?
  • Ephemeral/ Local
  • Context API
  • Usereducer hook
  • Action - reducer w/o redux
  • Action - reducer with redux
CSS?
  • Styled components
  • CSS Modules
  • Other
Host?
  • Gh pages
  • Other
Persist data?
  • Hooks in local storage
  • Redis External
Static type checking?
  • Lint
  • Typescript
Data Visualization?
  • D3
  • Recharts

UI

Layout?
  • React bootstrap
  • Material UI
Responsiveness?
  • Mobile-first
  • Responsive
  • Adaptive
Browser support?
  • All
  • Babel
Data Visualization?
  • D3
  • Recharts

Best Practices

List out features
  • Todo feature list
Test cases?
  • Unit
  • Integration
  • e-to-e
Performance
  • Client
  • Network
  • Backend
Security
  • Injections
  • XSS + CSRF
  • Access control
A11Y
Folder structure
  • Naming conventions? comments?

Extras

  • AWS
  • SSH
  • Docker
  • CI/CD

Screenshots:

Screenshot 1

Screenshot 2

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify