Skip to content

codingmster1/my-pokedex-react

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

How do you explain the huge gap in my resume cough github pushes/commits? This big ole project!

Screen Shot 2024-08-01 at 1 56 50 AM

Screen Shot 2024-08-01 at 1 57 14 AM

This project fetches pokemon data from the pokeapi with thousands of assets I uploaded into the project that were rendered according to the species

Screen Shot 2024-08-01 at 1 57 41 AM

It even has a working google log in to allow you to save your favorite pokemon in your own personal list!

Screen Shot 2024-08-01 at 2 02 06 AM

The original project creator didn't allow for mobile responsiveness so I added a working hamburger menu that hides the navbar and utilizes a menu backdrop to allow smaller devices to use it accordingly

Screen Shot 2024-08-01 at 2 04 39 AM

Screen Shot 2024-08-01 at 2 05 05 AM

Screen Shot 2024-08-02 at 2 14 59 PM

Also has a working Search Bar!

Screen Shot 2024-08-02 at 2 11 34 PM

Screen Shot 2024-08-02 at 2 12 45 PM

The reason I didn't push this project to github the moment of creation was due to the fact I had to find a workaround to deploy the working project with the large number (thousands of images!) of assets - so I deployed to netlify first and was able to utilize the gitignore file to not push the assets with all the project code into github all while having a working project.

Getting Started with Create React App

This project was bootstrapped with Create React App, using the Redux and Redux Toolkit TS template.

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.