If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
⚠️ Warning
```
Failed to update the yarn.lock, please update manually before merging.
```
Vulnerabilities that will be fixed with an upgrade:
Snyk has created this PR to fix 5 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
frontend/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory. If you are not using zero-install you can ignore this as your flow should likely be unchanged.⚠️ Warning
``` Failed to update the yarn.lock, please update manually before merging. ```Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-PRISMJS-1076581
SNYK-JS-PRISMJS-1585202
npm:marked:20180225
SNYK-JS-PRISMJS-597628
SNYK-JS-PRISMJS-1314893
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:
🦉 Regular Expression Denial of Service (ReDoS) 🦉 Cross-site Scripting (XSS)