A website where you can read and share spoilers of your favorite movies. Created with React.js and a firestore database.
Spoiler Zone uses:
- React 17.0.1
- React Router 5.2.0
- GitHub Pages 3.1.0
- Firebase 8.2.1
- NPM 6.14.10
- Node 14.15.4
This website uses a server to manage the API fetch calls, mainly for security reasons. You can check it at https://github.com/almirleandro/spoilerzone-server
All the technical information about movies in this website is from The Movie Database API. The API key is stored as an environment variable in Heroku.
The spoilers, on the other hand, are stored in a Firebase database, which is also called from the server, not from the front end. The path for the configuration of the Firebase package is stored as an environment variable too.
CORS, Helmet and Express Rate Limit were used as tools to ensure the security of the server, which, just as the Firebase database, is configured to receive calls only from the original website.
The code for testings can be found in the file App.test.js. In the project directory, you can run npm test, which Launches the test runner in the interactive watch mode.
You can also run npm test -- --coverage to include a coverage report to the test.
See the section about running tests for more information.
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.
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 this section about deployment for more information.
Builds the app for production and deploys it to GitHub Pages.
Before you use this command, you need to change package.json to use your own GitHub profile. You will find all the steps to do it in this link.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Any kind of contributions is welcome. If you encounter any bug, please raise an issue. Pull Requests are also great. Please, in any of these cases, try to be explicit about what is the issue or the PR about.