Additional Section in README.md file illustrating some issues encountered and their preventive measures

[rks-031]

Issue 1.

After forking the repo and cloning the repo to the local device, when we follow the steps given in the readme, i.e,
cd client ->npm install ->cd ../server ->npm install ->npm run start

We get an error message saying: Missing script: “start” and many others as shown below:

The error message indicates that the npm script "start" is missing in the project's package.json file.
When we run the command npm run start, npm looks for a script named "start" in the "scripts" section of the package.json file.

To resolve this issue, we can do one of the following:

a] Checking the package.json file: Open the package.json file located in the project's root directory and ensure a "scripts" section with a "start" script is defined. Make sure the "start" script is defined correctly. If it's missing, we need to add it.

b] Using a different script: If we intend to run a separate script instead of "start", we can modify the npm command accordingly. For example, if we have a script named "dev," we can run npm run dev instead.

After making the necessary changes, save the package.json file and try rerunning the command.

---

Issue 2.

After implementing the above-mentioned changes when we try to run the command: npm run start, we may get the following message on the console:
Server is running on 5000
error occured while connecting

The same message may also appear if we try to run the project using the npm run dev command.

Here's how we can prevent it:

We can modify the method by which the index.js file is listening to the port by implementing the environment variable PORT so that the server can automatically find an available port for it and if not then it has the localhost as 5000.

---

Thus, all these issues and their preventive measures should be mentioned in the README.md file by adding a specific section in it to help any user experiencing the same issues. An instance is shown below: