updates to handle npm vulnerability warnings #168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE:
This build requires Node 14 but currently for the luti production Netlify is installing deprecated Node v10.24.1
preview of this branch is here on my Netlify --> https://62cdc2e883f7030009597f95--incredible-narwhal-2054b9.netlify.app/
Node 10 might be getting set by an environment var in Netlify dashboard under
Build & Deploy
andEnvironment
- I have nothing set there and it installed Node 16.16.0 by default..Description:
some npm package updates (and small code change) to get rid of npm vuln warnings
I did a quick QA check and looks good BUT not sure I'm aware of all the latest features these days! So might want to take this for a quick spin before merging.
No rush if this is inconvenient but these vuln warnings have been popping off and climbing in number for awhile so felt like smashing them 🔨
folks will likely need to
rm -rf node_modules
andrm package-lock.json
before runningnpm install