Fixing installation issues and updating readme to address the issue,

[xXxSpicyBoiiixXx]

Description

(insert summary)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[elegantmoose]

@xXxSpicyBoiiixXx , few notes:

• I noted some typos
• This may be better fit in the Magma repo, as node specific.
• @clenk , thoughts? Im on the fence as this is very general to node, not Caldera.

[clenk]

What specific issues were encountered?

Maybe the readme just needs to mention npm as a requirement, like
* NodeJS (v16+ recommended) and npm
It's included in Node, but we can make it explicit.

More detailed instructions like this should go in fieldmanual in my opinion.

[xXxSpicyBoiiixXx]

I was downloading this on some Linux machines I have, there was some issues with node but I think making it explicit would be nice in the readme. I would agree it's not caldera specific but it does leverage node, but I still had to update all that and it was a bit of work to get caldera to work properly without it noted.

[clenk]

Any chance you can remember which versions of npm/node were giving you errors?

[xXxSpicyBoiiixXx]

I'm not sure about the version, but the latest one works.