App must run without using npm install --legacy-peer-deps

[palisadoes]

Is your feature request related to a problem? Please describe.

1. The app depends on legacy dependencies
2. The app must be upgraded to not use --legacy-peer-deps

Describe the solution you'd like

1. Upgrade app packages to not require the --legacy-peer-deps qualifier when running npm install
2. Update the INSTALLATION.md file with the new installation process just using npm install
3. The npm install must not redirect to npm install --legacy-peer-deps in any hidden way.
4. npm install --legacy-peer-deps must not be invoked in any way behind the scenes to install the latest required packages
5. All existing tests must pass
6. No functionality must be removed

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• See above

Additional context

• N/A

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

[git-init-priyanshu]

I would like to work on this issue.

[dhiraj0911]

Hey I'd like to work on this issue too

[git-init-priyanshu]

Hey @palisadoes, I have fixed the issue by uninstalling the package enzyme-adapter-react-16 and using @wojtekmaj/enzyme-adapter-react-17 (which was already installed and correctly used in place of the previously mentioned package). I am no longer getting errors with peer dependency, but I am receiving several warnings. Should I also resolve those warnings?

[palisadoes]

Yes. There should be no warnings. We should not be using deprecated or outdated packages. Open a PR when done

[palisadoes]

Also, determine the latest version of node that the app will work with and add it to the INSTALLATION.md file under the node installation section.

We need to state what our recommended version of node should be

[git-init-priyanshu]

Got it

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.