🔥🔥NOTE🔥🔥 IN THE ABOVE FOLDERS, THERE ARE FILES CALLED KEYS.JS AND USEGOOGLESEARCH.JS , where u have to input your own api key and context keyfrom Google developer page , else if u fork or pull this repository, it won't work
I have hosted the web app in google fire base("I used google to host google " XXD) . Hence i cannot share firebase files and the link of the app but you can have the preview of the application in the preview folder.
The google custom searvh api allows only 100 searches per day, thats a limition from the api side but thats okay for standard day to day user.
U can easily host your app on firebase using powershell/terminal and simple instructions on google firebase website
Feel free to make changes in the the repository branches to add upgrades :)
In the project directory, you can run:
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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.
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.