Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [BUG] - Missing Frontend Dependencies on Fresh Repository Clone #764

Open
Rucha-Ambaliya opened this issue Feb 16, 2025 · 8 comments
Open
Labels
bug Something isn't working

Comments

@Rucha-Ambaliya
Copy link
Contributor

Description

Issue

When I cloned the repository for the first time and configured it for development, the following dependencies were missing in the frontend, even though they were imported:

  • @fortawesome/fontawesome-svg-core
  • @fortawesome/free-solid-svg-icons
  • @fortawesome/react-fontawesome
  • i18next
  • i18next-http-backend
  • react-i18next

Proposed Solution

  1. Add package.json inside the frontend/ directory so that these dependencies install automatically with npm install.

    OR

  2. Update README.md with documentation on this error and how to install these packages locally:

    npm install @fortawesome/fontawesome-svg-core @fortawesome/free-solid-svg-icons @fortawesome/react-fontawesome
    npm install i18next i18next-http-backend react-i18next
    
    

Reproduction steps

Follow fresh installation steps to clone repository from starting

Logs

Browsers

No response

OS

No response

@Rucha-Ambaliya Rucha-Ambaliya added the bug Something isn't working label Feb 16, 2025
@Rucha-Ambaliya
Copy link
Contributor Author

@yassinedorbozgithub

@yassinedorbozgithub
Copy link
Collaborator

@yassinedorbozgithub

Can you please attach a screenshot to the issue that you have locally

@Rucha-Ambaliya
Copy link
Contributor Author

Rucha-Ambaliya commented Feb 18, 2025

@yassinedorbozgithub

issue 1

here is the ss for missing dependency @fortawesome/fontawesome-svg-core @fortawesome/free-solid-svg-icons @fortawesome/react-fontawesome

I had forgotten to get ss for another one!

@yassinedorbozgithub
Copy link
Collaborator

Hi @Rucha-Ambaliya, i suggest to run those commands and check if the issue persist

hexabot stop

rm -rf node_modules/ (root level)

cd frontend

rm -rf node_modules/

cd ..

npm cache clean --force

npm install

hexabot dev

@Rucha-Ambaliya
Copy link
Contributor Author

Rucha-Ambaliya commented Feb 19, 2025

So sorry for the late reply, I was a bit busy with my college work.

Issue with Module Inconsistency and Missing Dependencies

I tried the steps you mentioned, but it resulted in module inconsistencies. To ensure a clean setup, I cloned the repository again and started from scratch. However, the same issue persisted.

I believe the problem is related to version compatibility and missing packages.

1. Error Encountered:

../node_modules/@fortawesome/react-fontawesome/index.es.js:1:1
Module not found: Can't resolve '@fortawesome/fontawesome-svg-core'

Reference: Screen shot

Upon checking package.json, I noticed that @fortawesome/free-solid-svg-icons and @fortawesome/react-fontawesome (line 24 25) are present:

"@fortawesome/free-solid-svg-icons": "^6.5.2",
"@fortawesome/react-fontawesome": "^0.2.0"

However, @fortawesome/fontawesome-svg-core is missing.

Solution:

I ran the following command to install the missing package inside frontend folder:

npm install @fortawesome/fontawesome-svg-core

This resolved the issue.

2. Another Missing Package:

I encountered another error:

Module not found: Can't resolve 'i18next'
   8 |
   9 | // Core i18next library.
> 10 | import i18n from "i18next";
     | ^
  11 | import Backend from "i18next-http-backend";
  12 | // Bindings for React: allow components to
  13 | // re-render when language changes.

Reference: Screen shot

Upon checking package.json, I noticed that i18next-http-backend (line 36) is present:

"i18next-http-backend": "^2.6.2",

However, i18next itself is missing.

Solution:

I ran:

npm install i18next

This resolved the issue.

Conclusion:

Two packages are missing in frontend/package.json:

  1. @fortawesome/fontawesome-svg-core
  2. i18next

To prevent this issue, they should be explicitly added to package.json to avoid installation errors in future setups.

@yassinedorbozgithub
Copy link
Collaborator

So sorry for the late reply, I was a bit busy with my college work.

Issue with Module Inconsistency and Missing Dependencies

I tried the steps you mentioned, but it resulted in module inconsistencies. To ensure a clean setup, I cloned the repository again and started from scratch. However, the same issue persisted.

I believe the problem is related to version compatibility and missing packages.

1. Error Encountered:

../node_modules/@fortawesome/react-fontawesome/index.es.js:1:1
Module not found: Can't resolve '@fortawesome/fontawesome-svg-core'

Reference: Screen shot

Upon checking package.json, I noticed that @fortawesome/free-solid-svg-icons and @fortawesome/react-fontawesome (line 24 25) are present:

"@fortawesome/free-solid-svg-icons": "^6.5.2",
"@fortawesome/react-fontawesome": "^0.2.0"
However, @fortawesome/fontawesome-svg-core is missing.

Solution:

I ran the following command to install the missing package inside frontend folder:

npm install @fortawesome/fontawesome-svg-core
This resolved the issue.

2. Another Missing Package:

I encountered another error:

Module not found: Can't resolve 'i18next'
   8 |
   9 | // Core i18next library.
> 10 | import i18n from "i18next";
     | ^
  11 | import Backend from "i18next-http-backend";
  12 | // Bindings for React: allow components to
  13 | // re-render when language changes.

Reference: Screen shot

Upon checking package.json, I noticed that i18next-http-backend (line 36) is present:

"i18next-http-backend": "^2.6.2",
However, i18next itself is missing.

Solution:

I ran:

npm install i18next
This resolved the issue.

Conclusion:

Two packages are missing in frontend/package.json:

  1. @fortawesome/fontawesome-svg-core
  2. i18next

To prevent this issue, they should be explicitly added to package.json to avoid installation errors in future setups.

Hi @Rucha-Ambaliya, thanks for the details

@Rucha-Ambaliya
Copy link
Contributor Author

No, problem! Let me know if I should work on adding those packages!

@Rucha-Ambaliya
Copy link
Contributor Author

@yassinedorbozgithub Should I work on it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants