code100x / daily-code

https://projects.100xdevs.com/
590 stars 724 forks source link

bug: Disable Login Requirement During Development Phase Due to Authentication Issues and Local Database on the `LessonView` #437

Closed SOUMITRO-SAHA closed 1 month ago

SOUMITRO-SAHA commented 1 month ago

Describe the bug When users visit https://projects.100xdevs.com/ and browse through the posts, they are required to log in, which is understandable for the production environment. However, during the development phase, this requirement is not practical since the application is running on a local development database. Additionally, the Google login is not functioning correctly in the development setup, likely because the authentication route isn't configured for localhost:3000. It would be beneficial to remove the login requirement during the development phase.

To Reproduce Steps to reproduce the behavior:

  1. Go to https://projects.100xdevs.com/ without logging in, or use incognito mode.
  2. Open any article.
  3. Navigate to page 2 or beyond.
  4. You will encounter the Login Dialog, even in the development setup.

Expected behavior The login requirement should be disabled during the development phase, as it does not serve a useful purpose.

Screenshots or GIFs If applicable, add screenshots to help explain your problem. image

Info (please complete the following information):

Additional context Add any other context about the problem here.

ayesparshh commented 1 month ago

Screenshot 2024-05-20 145619 sorry for offtopic question im getting this error after running the repo please help, not able to run the code due to this error

t007rushi commented 1 month ago

@ayesparshh This happens many times just try take latest pull remove package-lock.json and node_modules

rm -rf node_modules 
rm package-lock.json

and npm install

SOUMITRO-SAHA commented 1 month ago

Essentially, MODULE_NOT_FOUND indicates an issue with your node_modules. This repository uses yarn, so please use yarn.

If you encounter any issues, follow @t007rushi 's advice: first, remove node_modules, pull the latest updates, and then run yarn

ayesparshh commented 1 month ago

it did worked thanks @SOUMITRO-SAHA @t007rushi