peacexoom / animehub Goto Github PK

Setup dockerfile for both frontend and backend seperately. Frontend image should contain only react. Backend image should contain both the NodeJS server and MySQL server. As a follow up you can also add docker-compose files to manage the containers.

i have cloned this. but the website is not running. it is throwing this error in the terminal even after following all the steps.

npm run start

start
nodemon server.js

[nodemon] 3.0.1
[nodemon] to restart at any time, enter rs
[nodemon] watching path(s): .
[nodemon] watching extensions: js,mjs,cjs,json
[nodemon] starting node server.js
Error: Access denied for user ''@'localhost' (using password: NO)
UNHANDLED REJECTION! 💥 Shutting down...
[nodemon] app crashed - waiting for file changes before starting...

HOW TO FIX THIS?

We should use Data layer api's rather than browserRouter since it will improve the performance of the App and provide additional functionalities.

Whenever the user clicks this (Hi, Username) button the user should be redirected to a page where there will be charts and stats about his/her watchlist.

This looks a little weird buttons spreading like this. Also make genre buttons in this section just like in the main genre page(a little bit heightened and add hover effect)

kindly assign me this issue under hacktoberfest tag

Currently, the user's passwords are being stored in the DB as strings which is not a good practice considering security reasons.

We can hash the password and then store the hash in the DB.

Please assign this issue to me under Hacktoberfest, I would like to work on this.

Desktop view:

Mobile view:

The black gradient on animecard should only be applied to the bottom half part of the card.

Anime added to the bookmark list are not shown in the bookmark list.

All the router are implemented in server.js which makes the app clunky. Create a seperate routes directory to make the code more organized.

Description: Introduce code in app.js to robustly handle unhandled promise rejections, uncaught exceptions, and unhandled routes.

Is your feature request related to a problem? Please describe.
In our Node.js server, we've identified instances of unhandled promise rejections, uncaught exceptions, and requests to unhandled routes. These pitfalls can compromise the server's reliability and security. By addressing these directly in app.js, we aim to reinforce our server's resilience.

Describe the solution you'd like
In the app.js:

1. Unhandled Promise Rejections:

   • Explanation: When we have an error in the .env file then we may encounter the unhandled promise rejection error.
   • Solution: Prevent the server crash by closing the server gracefully

2. Uncaught Exceptions:

   • Explanation: Exceptions that aren't caught in try-catch blocks might crash the server.
   • Example: Imagine having a console.log(abfgvhgvd)
   • Solution: Integrate a handler in app.js to log it and close the server gracefully

3. Unhandled Routes:

   • Explanation: Requests to undefined routes can leak information or confuse users.
   • Example: A user who entered wrong route like localhost:3000/api/contests/random-msg
   • Solution: Set up a final route handler to return a standardized 404 Not Found response and inform the user about checking the route

Describe alternatives you've considered

• For unhandled promise rejections and exceptions, we could use real-time error monitoring tools like Sentry for immediate alerts.
• For unhandled routes, establishing an analytics tool could give insights into frequent unrecognized route requests, helping to understand user patterns or detect malicious actors.

Additional context
Embedding these error-handling measures into our primary server file, app.js, is crucial for a robust server environment. It aids in preemptively addressing common pitfalls, ensuring a smoother user experience and providing developers with valuable error context.

Hello There,
Myself Jay Trivedi . I have made changes in the index.js . I have added a token system which will be send to the user at the time of the authentication . When users click the link, your server should validate the token on the backend before confirming the email.

Hope this changes find you well.

Thank you
Regards

I'd suggest changing 'submit' on the register screen to 'register, and Also swap the places of the login and submit to be more intuitive - "continue the same path" should be on the right and "go back/do something else" should be on the left. (Same goes for the login screen)
I already have it done on my branch, you can just assign me the issue if you agree and I'll put up a PR

Give a proper description of each optimization you do.

Add numberings in aim to see animes or a functionality such that user can prioritize the animes in there aim to see list

I provide a setup for the graceful shutdown on the server side. To prevent close/exit commands forcefully, especially on database queries. For more here
Can you assign this issue to me @Peacexoom @moonpatel ??

Add suggestions for search query as the user enters text into the search bar.

the password field doesn't seem to accept symbols - but it gives the error of Must contain at least one capital letter, small letter and a digit
kept me confused for a bit but then i realized the issue was that i had ! in my password, so the verification proccess need a small adjustment - either modify the message that symbols are not allowed, or allow symbols.

If a new user create an account for the first time, a link should be sent in the email. And only after clicking on the link and verifying their email, user can move forward.

Images in animecard are not proper and also improve the animation when we hover on an animecard(maybe add time duration)

The anime name is not readable beacuase of its font color. Add a black gradient at the bottom of the anime card to make the text readable.

User should be able to categorize it's watchlist in three section: finished, watching and aim to see. You could add these kind of buttons:

I see you're using absolute path inside . Using relative path will be better has the app expands it's easier to maintain