[Snyk] Fix for 2 vulnerabilities - #597
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-FASTXMLPARSER-15155603 - https://snyk.io/vuln/SNYK-JS-LODASH-15053838
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7cb7410eb5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "engines": { | ||
| "node": ">=20.0.0" | ||
| } |
There was a problem hiding this comment.
Declare Node >=20 requirement introduced by aws-sdk
The aws-amplify upgrade now pulls in AWS SDK clients that declare engines.node >=20 (e.g., this @aws-sdk/client-firehose entry). If the app is built or deployed on Node 18 (a common default when package.json doesn’t set engines), installs can fail under engine-strict or modules can crash at runtime due to unsupported syntax. Consider explicitly declaring Node >=20 (or constraining the dependency) to avoid environment-dependent failures.
Useful? React with 👍 / 👎.
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-FASTXMLPARSER-15155603
SNYK-JS-LODASH-15053838
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Uncaught Exception
🦉 Prototype Pollution