Update node

[hcorson-dosch-usgs]

This PR updates our npm configuration to use node version 20 and re-point the docker build to debian:stable, because debian:stretch has been deprecated.

To test

1. Get off VPN if you are on VPN
2. Check what version of node you are using by running node -v
3. If not using version 20, switch to node version 20 by running nvm use 20 [If it's not installed, install latest version of node by running nvm install 20.0.0 --reinstall-packages-from=14.17.0]
4. Run npm install
5. Run npm run serve

Changes:

• In Dockerfile, point to to a stable debian release, instead of the archived stretch release, using the debian:stable tag listed as a current tag on Dockerhub.
• In Dockerfile, get and install the current version of node (version 20)
• In package.json remove addition of node-sass in devDependencies and instead specify latest version of sass, as node-sass is not supported for node 20. Node-sass is now deprecated, and the makers recommend switching to sass
• In package.json add env NODE_OPTIONS=--openssl-legacy-provider to all 'serve' and 'build' scripts to overcome a lack of support for digital envelope routines in node 17+. See this issue and this comment
• Update other miscellaneous packages to match versions used in more recently built and updated package.json in what-is-drought
• Add .npmrc file in root directory with the content legacy-peer-deps=true to overcome peer dependency conflicts between cli-plugin-eslint, eslint, and babel-eslint. See this issue and this comment.
• Changes to other files due to running lint:

---

First . . .

• [X] Clean the code the way Vue likes it - run 'npm run lint --fix'
• [ ] Make sure all tests run

Then check for accessibly compliance

• [ ] Run WAVE plugin 508 compliance tool

Then run Browserstack; check that application works on . . .

• [X] Chrome
• [ ] Safari
• [X] Edge
• [X] Firefox
• [ ] Samsung Internet
• [ ] Internet Explorer 11 (not supported, but still needs at least a working user redirect page)

Finally . . .

• [ ] Update the changelog appropriately

After making a pull request

• [ ] If appropriate, put the link to the PR in the ticket
• [X] Assign someone to review unless the change is trivial

[hcorson-dosch-usgs]

This worked. Thank you.

No prob!

So the env NODE_OPTIONS=--openssl-legacy-provider piece is related to versioning changes b/w node and webpack?

Right - sounds like node changed to a later version of OpenSSL, which broke some part of webpack, and you have to use this workaround. It looked like webpack wasn't included in this package.json, but I opted to include the workaround just in case and so that we have a consistent set-up across our builds.