Fix frontend to run using yarn

[Hasteerp]

Terms

• I have searched all open bug reports
• I agree to follow activist's Code of Conduct

Behavior

Current Behavior:

When you follow the steps under Contributing.md to run frontend using Yarn. It gives the following error.

The error suggests too many open files. Possible error is too many file watchers.

Expected Behavior:

Frontend should run locally using yarn. It should run without file watchers or an option to turn off these file watchers when trying to run locally. It should not try to open watchers in node_modules.

[andrewtavis]

Thanks a lot for this issue, @Hasteerp! Would you have interest in looking in to this? We can also save it till you're done with the other issue.

[Hasteerp]

Sure @andrewtavis , I would be happy to take this up once I am done working on the other issue.
But feel free to assign it to someone else if someone shows interest :)

[andrewtavis]

Let's write when you're done with the other one then :) Thanks again!

[cquinn540]

Found what I think is the root cause: nuxt/nuxt#29744

I tried changing package.json to include:

  "resolutions": {
    "chokidar": "3.6.0",
    "playwright-core": "1.45.1"
  }

Reran yarn install I can start the frontend locally now. Can't fully test it because my backend keeps crashing:

django_backend  | Traceback (most recent call last):
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 105, in _execute
django_backend  |     return self.cursor.execute(sql, params)
django_backend  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  | psycopg2.errors.UndefinedTable: relation "entities_groupfaq" does not exist
django_backend  | LINE 1: DELETE FROM "entities_groupfaq" WHERE "entities_groupfaq"."g...
django_backend  |                     ^
django_backend  |
django_backend  |
django_backend  | The above exception was the direct cause of the following exception:
django_backend  |
django_backend  | Traceback (most recent call last):
django_backend  |   File "/app/manage.py", line 27, in <module>
django_backend  |     main()
django_backend  |   File "/app/manage.py", line 23, in main
django_backend  |     execute_from_command_line(sys.argv)
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
django_backend  |     utility.execute()
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/core/management/__init__.py", line 436, in execute
django_backend  |     self.fetch_command(subcommand).run_from_argv(self.argv)
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/core/management/base.py", line 413, in run_from_argv
django_backend  |     self.execute(*args, **cmd_options)
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/core/management/base.py", line 459, in execute
django_backend  |     output = self.handle(*args, **options)
django_backend  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/app/backend/management/commands/populate_db.py", line 45, in handle
django_backend  |     UserModel.objects.exclude(username="admin").delete()
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 1188, in delete
django_backend  |     deleted, _rows_count = collector.delete()
django_backend  |                            ^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/deletion.py", line 472, in delete
django_backend  |     count = qs._raw_delete(using=self.using)
django_backend  |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 1210, in _raw_delete
django_backend  |     cursor = query.get_compiler(using).execute_sql(CURSOR)
django_backend  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql
django_backend  |     cursor.execute(sql, params)
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 122, in execute
django_backend  |     return super().execute(sql, params)
django_backend  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 79, in execute
django_backend  |     return self._execute_with_wrappers(
django_backend  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
django_backend  |     return executor(sql, params, many, context)
django_backend  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 100, in _execute
django_backend  |     with self.db.wrap_database_errors:
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__
django_backend  |     raise dj_exc_value.with_traceback(traceback) from exc_value
django_backend  |   File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 105, in _execute
django_backend  |     return self.cursor.execute(sql, params)
django_backend  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[cquinn540]

destroying and recreating my environment with docker-compose rm -f -v --env-file .env.dev fixed the database issue I ran into

[andrewtavis]

Do you think anything else is needed here, @cquinn540?