[Snyk] Upgrade local-web-server from 5.3.1 to 5.4.0 #18
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.
Snyk has created this PR to upgrade local-web-server from 5.3.1 to 5.4.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 4 versions ahead of your current version.
The recommended version was released on a month ago.
Issues fixed by the recommended upgrade:
SNYK-JS-75LBDEEPMERGE-7575311
Release notes
Package name: local-web-server
-
5.4.0 - 2024-08-01
- If your local
- Max body-parser file size is now 500MB by default (previously, lws would throw an error if attempting to parse a file greater than 1MB). #130
- Prevent stored config being parsed twice. Fixes #176
- Dependencies upgraded to address security warnings within the dep tree.
-
5.3.4 - 2024-07-20
-
5.3.3 - 2024-03-31
-
5.3.2 - 2024-03-31
-
5.3.1 - 2024-01-08
from local-web-server GitHub release notesThere were no breaking changes to the API, the minimum version of Node is still v12.20.
Bug fixes
wsconnection is insecure (HTTP) and you're rewriting one or more routes to a secure (HTTPS/HTTP2) remote server, if the remote response sets a cookie with the attributesecurethen that attribute is removed (which is necessary else the browser will refuse to store it via an insecure connection). With this new release, lws-rewrite also removesSameSite=noneif it is set alongsidesecure. See lwsjs/rewrite#14.5.3.4
5.3.3
5.3.2
5.3.1
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: