Updates dependencies and ups version to 0.0.10

[nigelmegitt]

Tracking pull request, addresses vulnerabilities

[danielthepope]

I followed the Setup instructions in the README.

When I run npm install, I get the message

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

After it has installed, the lockfileVersion gets set to 1, so perhaps something isn't documented correctly?

npm --version gives me 6.14.11, which is the one installed when I ran nvm install 14.16.0. Perhaps you also need to add how to update NPM? I think it's npm install -g npm

[nigelmegitt]

Thanks @danielthepope I think I've built it with a more recent version of npm (7.24.2) so that might explain the unnecessary discrepancy. I either update the README minimum node version, or install the older version and use that to rebuild it, I suppose!

[danielthepope]

I would suggest using whatever is being offered in the latest LTS release, but I'm not up to date with "how things are developed in Node", so I think you should ask someone who is more in the know. e.g. are there security implications with using the older version of NPM?

[nigelmegitt]

I've switched to the latest LTS version of nvm, which is currently 14.8.1, and the latest version of npm, which is 8.1.1 and updated the README to reflect those, so hopefully that will address your comments @danielthepope

The suggestion in the README is now to use nvm install-latest-npm as a setup step, which is probably the easiest way to upgrade npm.

[danielthepope]

OK, that's much better. The only thing I would point out now is the version mismatch between package.json and package-lock.json. When I ran npm install it updated the version in package-lock.json - and I think that new version should be part of this PR.