[#74] Update Node

[malparty]

• Close Update to Node 22 #74

What happened 👀

• Use Node 22
• Update some dependencies
• Resolved vulnerabilities from dependencies

Insight 📝

I'm not sure how to "test" these versions on my project, without publishing the npm package first... So if you know, let me know so I can test before we merge :harold:

Proof Of Work 📹

Before	After

[jtotty]

@malparty Just throwing an idea here: you can try using npm-link to test the packages locally in a repository that is dependent on them before publishing. I'm just quickly checking if it actually works.

https://docs.npmjs.com/cli/v9/commands/npm-link

[jtotty]

@malparty There's two ways you can do this locally with npm-link or npm-pack. While this requires manual testing and isn't the most reliable approach, it's an option.

npm-link
Creates a symlink to the package.
https://docs.npmjs.com/cli/v9/commands/npm-link

1. In the individual package directory run npm link.
2. cd into the root directory of a project and make sure you are using the correct nodejs version. Note: If you are using a version manager like nvm or asdf it won't use the symlinked package if there is a node version mismatch. It will install the published package specified in package.json as standard.
3. Delete the node_modules folder
4. Run npm link @nimblehq/eslint-config-nimble-core - this runs npm install and uses the symlinked package.

To unlink run npm unlink --no-save @nimblehq/eslint-config-nimble-core

npm-pack
Create a tarball from a package
https://docs.npmjs.com/cli/v9/commands/npm-pack

1. In the individual package directory run npm pack --pack-destination <filepath>
2. Update the package.json in the project to use the tarball. E.g. "@nimblehq/eslint-config-nimble-core": "file:~/temp_npm_pack/nimblehq-eslint-config-nimble-core-2.8.2.tgz"
3. Delete the node_modules folder
4. Run npm install