Many packages in package.lock are deprecated or otherwise not reccomended

[voidarclabs]

To test changes locally, without docker installed, the official instruction is to run npm install and then npm run to start a server on port 3000. First of all, there is no longer an "npm start" script, instead being npm build and then npm dev to achieve the same effect. This being a docs issue, I will leave it at face value and continue with the subject matter.

When running aforementioned "npm install" command, it first gives the error that some packages are unable to be resolved: Then, when running with --force (definitely not reccomended), it gives numerous warnings about deprecated packages:

This could be fixed by either changing the docs to match these changes, or updating the version numbers in package.lock. Thought this was issue worthy.

Cheers!

[potts99]

will look into this