Bump the npm_and_yarn group across 2 directories with 20 updates
Type: Pull Request
State: Closed
Association: None
Comments: 1
(3 months ago)
(3 months ago)
(3 months ago)
dependencies javascript
Bumps the npm_and_yarn group with 8 updates in the /bin/Debug/net8.0/my-app directory:
| Package | From | To |
|---|---|---|
| express | 4.19.2 |
4.21.2 |
| braces | 3.0.2 |
3.0.3 |
| cookie | 0.4.2 |
0.7.1 |
| socket.io | 4.7.4 |
4.8.1 |
| esbuild | 0.19.11 |
0.25.9 |
| @angular-devkit/build-angular | 17.1.3 |
20.2.2 |
| ws | 8.11.0 |
8.17.1 |
| socket.io-adapter | 2.5.2 |
2.5.5 |
Bumps the npm_and_yarn group with 8 updates in the /wwwroot directory:
| Package | From | To |
|---|---|---|
| express | 4.19.2 |
4.21.2 |
| braces | 3.0.2 |
3.0.3 |
| cookie | 0.4.2 |
0.7.1 |
| socket.io | 4.7.4 |
4.8.1 |
| esbuild | 0.19.11 |
0.25.9 |
| @angular-devkit/build-angular | 17.1.3 |
20.2.2 |
| ws | 8.11.0 |
8.17.1 |
| socket.io-adapter | 2.5.2 |
2.5.5 |
Updates express from 4.19.2 to 4.21.2
Release notes
Sourced from express's releases.
4.21.2
What's Changed
- Add funding field (v4) by
@bjohansebasin expressjs/express#6065- deps: path-to-regexp@0.1.11 by
@blakeembreyin expressjs/express#5956- deps: bump path-to-regexp@0.1.12 by
@jonchurchin expressjs/express#6209- Release: 4.21.2 by
@UlisesGasconin expressjs/express#6094Full Changelog: https://github.com/expressjs/express/compare/4.21.1...4.21.2
4.21.1
What's Changed
- Backport a fix for CVE-2024-47764 to the 4.x branch by
@joshbukerin expressjs/express#6029- Release: 4.21.1 by
@UlisesGasconin expressjs/express#6031Full Changelog: https://github.com/expressjs/express/compare/4.21.0...4.21.1
4.21.0
What's Changed
- Deprecate
"back"magic string in redirects by@blakeembreyin expressjs/express#5935- finalhandler@1.3.1 by
@wesleytoddin expressjs/express#5954- fix(deps): serve-static@1.16.2 by
@wesleytoddin expressjs/express#5951- Upgraded dependency qs to 6.13.0 to match qs in body-parser by
@agadzinski93in expressjs/express#5946New Contributors
@agadzinski93made their first contribution in expressjs/express#5946Full Changelog: https://github.com/expressjs/express/compare/4.20.0...4.21.0
4.20.0
What's Changed
Important
- IMPORTANT: The default
depthlevel for parsing URL-encoded data is now32(previously wasInfinity)- Remove link renderization in html while using
res.redirectOther Changes
- 4.19.2 Staging by
@wesleytoddin expressjs/express#5561- remove duplicate location test for data uri by
@wesleytoddin expressjs/express#5562- feat: document beta releases expectations by
@marco-ippolitoin expressjs/express#5565- Cut down on duplicated CI runs by
@jonchurchin expressjs/express#5564- Add a Threat Model by
@UlisesGasconin expressjs/express#5526- Assign captain of encodeurl by
@blakeembreyin expressjs/express#5579- Nominate jonchurch as repo captain for
http-errors,expressjs.com,morgan,cors,body-parserby@jonchurchin expressjs/express#5587- docs: update Security.md by
@inigomarquinezin expressjs/express#5590- docs: update triage nomination policy by
@UlisesGasconin expressjs/express#5600- Add CodeQL (SAST) by
@UlisesGasconin expressjs/express#5433- docs: add UlisesGascon as triage initiative captain by
@UlisesGasconin expressjs/express#5605
... (truncated)
Changelog
Sourced from express's changelog.
4.21.2 / 2024-11-06
- deps: path-to-regexp@0.1.12
- Fix backtracking protection
- deps: path-to-regexp@0.1.11
- Throws an error on invalid path values
4.21.1 / 2024-10-08
- Backported a fix for CVE-2024-47764
4.21.0 / 2024-09-11
- Deprecate
res.location("back")andres.redirect("back")magic string- deps: serve-static@1.16.2
- includes send@0.19.0
- deps: finalhandler@1.3.1
- deps: qs@6.13.0
4.20.0 / 2024-09-10
- deps: serve-static@0.16.0
- Remove link renderization in html while redirecting
- deps: send@0.19.0
- Remove link renderization in html while redirecting
- deps: body-parser@0.6.0
- add
depthoption to customize the depth level in the parser- IMPORTANT: The default
depthlevel for parsing URL-encoded data is now32(previously wasInfinity)- Remove link renderization in html while using
res.redirect- deps: path-to-regexp@0.1.10
- Adds support for named matching groups in the routes using a regex
- Adds backtracking protection to parameters without regexes defined
- deps: encodeurl@~2.0.0
- Removes encoding of
\,|, and^to align better with URL spec- Deprecate passing
options.maxAgeandoptions.expirestores.clearCookie
- Will be ignored in v5, clearCookie will set a cookie with an expires in the past to instruct clients to delete the cookie
Commits
1faf2284.21.22e0fb64deps: bump path-to-regexp@0.1.12 (#6209)59fc270deps: path-to-regexp@0.1.11 (#5956)51fc39cdocs: add funding (#6065)8e229f94.21.1a024c8afix(deps): cookie@0.7.17e562c64.21.01bcde96fix(deps): qs@6.13.0 (#5946)7d36477fix(deps): serve-static@1.16.2 (#5951)40d2d8ffix(deps): finalhandler@1.3.1- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by jonchurch, a new releaser for express since your current version.
Updates body-parser from 1.20.2 to 1.20.3
Release notes
Sourced from body-parser's releases.
1.20.3
What's Changed
Important
- deps: qs@6.13.0
- add
depthoption to customize the depth level in the parser- IMPORTANT: The default
depthlevel for parsing URL-encoded data is now32(previously wasInfinity). DocumentationOther changes
- chore: add support for OSSF scorecard reporting by
@inigomarquinezin expressjs/body-parser#522- ci: fix errors in ci github action for node 8 and 9 by
@inigomarquinezin expressjs/body-parser#523- fix: pin to node@22.4.1 by
@wesleytoddin expressjs/body-parser#527- deps: qs@6.12.3 by
@melikhov-devin expressjs/body-parser#521- Add OSSF Scorecard badge by
@bjohansebasin expressjs/body-parser#531- Linter by
@UlisesGasconin expressjs/body-parser#534- Release: 1.20.3 by
@UlisesGasconin expressjs/body-parser#535New Contributors
@inigomarquinezmade their first contribution in expressjs/body-parser#522@melikhov-devmade their first contribution in expressjs/body-parser#521@bjohansebasmade their first contribution in expressjs/body-parser#531@UlisesGasconmade their first contribution in expressjs/body-parser#534Full Changelog: https://github.com/expressjs/body-parser/compare/1.20.2...1.20.3
Changelog
Sourced from body-parser's changelog.
1.20.3 / 2024-09-10
- deps: qs@6.13.0
- add
depthoption to customize the depth level in the parser- IMPORTANT: The default
depthlevel for parsing URL-encoded data is now32(previously wasInfinity)
Commits
17529511.20.339744cfchore: linter (#534)b2695c4Merge commit from forkade0f3fadd scorecard to readme (#531)99a1bd6deps: qs@6.12.3 (#521)9478591fix: pin to node@22.4.183db46aci: fix errors in ci github action for node 8 and 9 (#523)9d4e212chore: add support for OSSF scorecard reporting (#522)- See full diff in compare view
Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for body-parser since your current version.
Updates braces from 3.0.2 to 3.0.3
Commits
74b2db23.0.388f1429update eslint. lint, fix unit tests.415d660Snyk js braces 6838727 (#40)190510ffix tests, skip 1 test in test/braces.expand716eb9freadme bumpa5851e5Merge pull request #37 from coderaiser/fix/vulnerability2092bd1feature: braces: add maxSymbols (https://github.com/micromatch/braces/issues/...9f5b4cffix: vulnerability (https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727)98414f9remove funding file665ab5dupdate keepEscaping doc (#27)- Additional commits viewable in compare view
Updates cookie from 0.4.2 to 0.7.1
Release notes
Sourced from cookie's releases.
0.7.1
Fixed
- Allow leading dot for domain (#174)
- Although not permitted in the spec, some users expect this to work and user agents ignore the leading dot according to spec
- Add fast path for
serializewithout options, useobj.hasOwnPropertywhen parsing (#172)https://github.com/jshttp/cookie/compare/v0.7.0...v0.7.1
0.7.0
- perf: parse cookies ~10% faster (#144 by
@kurtextremand #170)- fix: narrow the validation of cookies to match RFC6265 (#167 by
@bewinsnw)- fix: add
maintopackage.jsonfor rspack (#166 by@proudparrot2)https://github.com/jshttp/cookie/compare/v0.6.0...v0.7.0
0.6.0
- Add
partitionedoption0.5.0
- Add
priorityoption- Fix
expiresoption to reject invalid dates- pref: improve default decode speed
- pref: remove slow string split in parse
Commits
cf4658f0.7.16a8b8f5Allow leading dot for domain (#174)58015c0Remove more code and perf wins (#172)ab057d60.7.05f02ca8Migrate history to GitHub releasesa5d591cMigrate history to GitHub releases51968f9Skip isNaN9e7ca51perf(parse): cache length, return early (#144)d6f39b0Fix tests for old node6bb701fRemove failing scorecard- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by blakeembrey, a new releaser for cookie since your current version.
Updates socket.io from 4.7.4 to 4.8.1
Release notes
Sourced from socket.io's releases.
socket.io@4.8.1
Due to a change in the bundler configuration, the production bundle (
socket.io.min.js) did not support sending and receiving binary data in version4.8.0. This is now fixed.Dependencies
engine.io@~6.6.0(no change)ws@~8.17.1(no change)socket.io-client@4.8.1
Bug Fixes
- bundle: do not mangle the "_placeholder" attribute (ca9e994)
Dependencies
engine.io-client@~6.6.1(no change)ws@~8.17.1(no change)socket.io-client@4.8.0
Features
Custom transport implementations
The
transportsoption now accepts an array of transport implementations:import { io } from "socket.io-client"; import { XHR, WebSocket } from "engine.io-client";const socket = io({ transports: [XHR, WebSocket] });
Here is the list of provided implementations:
Transport Description FetchHTTP long-polling based on the built-in fetch()method.NodeXHRHTTP long-polling based on the XMLHttpRequestobject provided by thexmlhttprequest-sslpackage.XHRHTTP long-polling based on the built-in XMLHttpRequestobject.NodeWebSocketWebSocket transport based on the WebSocketobject provided by thewspackage.WebSocketWebSocket transport based on the built-in WebSocketobject.WebTransportWebTransport transport based on the built-in WebTransportobject.Usage:
Transport browser Node.js Deno Bun
... (truncated)
Commits
91e1c8bchore(release): socket.io@4.8.18d5528achore(release): socket.io-client@4.8.171387e5refactor(sio-client): reexport transports from the engineaead835refactor(sio): make Namespace._fns private (#5196)029e010chore(release): engine.io-client@6.6.24ca6ddbdocs(nuxt): update example with latest versionca9e994fix(sio-client): do not mangle the "_placeholder" attribute4865f2efix(eio-client): prevent infinite loop with Node.js built-in WebSocketd4b3ddeci: use Node.js 223b68658chore: bump@fails-components/webtransportto version 1.1.4 (dev)- Additional commits viewable in compare view
Updates esbuild from 0.19.11 to 0.25.9
Release notes
Sourced from esbuild's releases.
v0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:drive. The problem was as follows:
- Yarn in Plug'n'Play mode on Windows stores its global module cache on the
C:drive- Some developers put their projects on the
D:drive- Yarn generates relative paths that use
../..to get from the project directory to the cache directory- Windows-style paths don't support directory traversal between drives via
..(soD:\..is justD:)- I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with
C:\are actually Unix-style paths beginning with/C:/, so the../..path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }())// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
v0.25.8
Fix another TypeScript parsing edge case (#4248)
This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the
?:operator. The regression specifically involves parsing an arrow function containing a#privateidentifier inside the middle of a?:ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:
... (truncated)
Changelog
Sourced from esbuild's changelog.
Changelog: 2023
This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).
Commits
195e05cpublish 0.25.9 to npm3dac33ffix #3131, fix #3663: yarnpnp + windows + D drive0f2c5c8mock fs now supports multiple volumes on windows100a51esplit out yarnpnp snapshot tests13aace3removeC:assumption from windows snapshot testsf1f413ffix #4252: preserve parentheses around functions1bc8091fix #4257, close #4258: go 1.23.10 => 1.23.12bc52135move the go compiler version togo.versiona0af5d1makefile: useESBUILD_VERSIONconsistently8c71947publish 0.25.8 to npm- Additional commits viewable in compare view
Updates @angular-devkit/build-angular from 17.1.3 to 20.2.2
Release notes
Sourced from @angular-devkit/build-angular's releases.
20.2.2
@angular/cli
Commit Description don't set a default for array options when length is 0 set process title when running architect commands
@angular/build
Commit Description avoid extra tick in SSR dev-server builds maintain media output hashing with vitest unit-testing 20.2.1
@angular-devkit/schematics-cli
Commit Description correctly set default array values
@schematics/angular
Commit Description directly resolve karma config template in migration prevent AI config schematic from failing when 'none' and other AI tools are selected
@angular/cli
Commit Description correctly set default array values
@angular/build
Commit Description correct JS/TS file paths when running under Bazel ensure karma polyfills reporter factory returns a value 20.2.0
@schematics/angular
@angular/cli
... (truncated)
Changelog
Sourced from @angular-devkit/build-angular's changelog.
20.2.2 (2025-09-03)
@angular/cli
Commit Type Description a793bbc47 fix don't set a default for array options when length is 0 2736599e2 fix set process title when running architect commands
@angular/build
Commit Type Description 5c2abffea fix avoid extra tick in SSR dev-server builds f3c826853 fix maintain media output hashing with vitest unit-testing 21.0.0-next.1 (2025-08-27)
Breaking Changes
@angular/cli
- The
ngcommands will no longer automatically detect and usecnpmas the package manager. As an alternative use the.npmrcfile to ensure npm uses the cnpm registry.
@angular-devkit/schematics-cli
Commit Type Description aed26c388 fix correctly set default array values
@schematics/angular
Commit Type Description 4912f3990 feat add Tailwind CSS option to application schematic and ng new6c7b79833 fix directly resolve karma config template in migration 0f86cf878 fix prevent AI config schematic from failing when 'none' and other AI tools are selected
@angular/cli
Commit Type Description 0d53e82d5 feat provide detailed peer dependency conflict errors in ng add f513089e2 feat remove direct support for cnpm47d77a3ed fix correctly set default array values e5aed6d65 fix show planned actions in ng adddry run
... (truncated)
Commits
8ffc449release: cut the v20.2.2 release425bfe4refactor(@angular/cli): update MCP example tool format for if example2736599fix(@angular/cli): set process title when running architect commandsf3c8268fix(@angular/build): maintain media output hashing with vitest unit-testing99526bdrefactor(@angular/cli): Improve zoneless migration prompts based on observed ...b2d5e6erefactor(@angular/cli): add logging and HTML removal to doc search tool5c2abfffix(@angular/build): avoid extra tick in SSR dev-server builds0eaec23build: update github/codeql-action action to v3.30.0269fd99build: lock file maintenance2d8b6f6build: update pnpm to v10.15.1- Additional commits viewable in compare view
Updates http-proxy-middleware from 2.0.6 to 2.0.9
Release notes
Sourced from http-proxy-middleware's releases.
v2.0.9
What's Changed
- fix(fixRequestBody): check readableLength by
@chimuraiin chimurai/http-proxy-middleware#1097- chore(package): v2.0.9 by
@chimuraiin chimurai/http-proxy-middleware#1099Full Changelog: https://github.com/chimurai/http-proxy-middleware/compare/v2.0.8...v2.0.9
v2.0.8
What's Changed
- fix(fixRequestBody): prevent multiple .write() calls by
@chimuraiin chimurai/http-proxy-middleware#1090- fix(fixRequestBody): handle invalid request by
@chimuraiin chimurai/http-proxy-middleware#1091- chore(package): v2.0.8 by
@chimuraiin chimurai/http-proxy-middleware#1094Full Changelog: https://github.com/chimurai/http-proxy-middleware/compare/v2.0.7...v2.0.8
v2.0.7
Full Changelog: https://github.com/chimurai/http-proxy-middleware/compare/v2.0.6...v2.0.7
v2.0.7-beta.1
Full Changelog: https://github.com/chimurai/http-proxy-middleware/compare/v2.0.7-beta.0...v2.0.7-beta.1
v2.0.7-beta.0
Full Changelog: https://github.com/chimurai/http-proxy-middleware/compare/v2.0.6...v2.0.7-beta.0
Changelog
Sourced from http-proxy-middleware's changelog.
v2.0.9
- fix(fixRequestBody): check readableLength
v2.0.8
- fix(fixRequestBody): prevent multiple .write() calls
- fix(fixRequestBody): handle invalid request
v2.0.7
- ci(github actions): add publish.yml
- fix(filter): handle errors
Commits
617a7c9chore(package): v2.0.9 (#1099)d22d587fix(fixRequestBody): check readableLength (#1097)d03d51bchore(package): v2.0.8 (#1094)c50dd06fix(fixRequestBody): handle invalid request (#1091)76a9d8dfix(fixRequestBody): prevent multiple .write() calls (#1090)1e92339ci(github-actions): fix npm tag90afb7cchore(package): v2.0.70b4274efix(filter): handle errors1bd6dd5ci(github actions): add publish.yml- See full diff in compare view
Updates nanoid from 3.3.7 to 3.3.11
Release notes
Sourced from nanoid's releases.
3.3.11
- Fixed React Native support.
3.3.10
- Fixed React Native support (by
@steida).3.3.9
- Reduced npm package size.
Changelog
Sourced from nanoid's changelog.
3.3.11
- Fixed React Native support.
3.3.10
- Fixed React Native support (by
@steida).3.3.9
- Reduced npm package size.
3.3.8
- Fixed a way to break Nano ID by passing non-integer size (by
@myndzi).
Commits
37289ceRelease 3.3.11 version23690b7Fix CIc147962Fix RN supporta83734eMove to manually ESM/CJS dual packagebb12e8aRelease 3.3.10 version8f44264Fix Expo supportadf9b0cRelease 3.3.9 version1c6f088Remove dev file from npm package3044cd5Release 3.3.8 version4fe3495Update size limit- Additional commits viewable in compare view
Updates on-headers from 1.0.2 to 1.1.0
Release notes
Sourced from on-headers's releases.
1.1.0
Important
What's Changed
- Migrate CI pipeline to GitHub actions by
@carpassein jshttp/on-headers#12- fix README.md badges by
@carpassein jshttp/on-headers#13- add OSSF scorecard action by
@carpassein jshttp/on-headers#14- fix: use
ubuntu-latestas ci runner by@UlisesGasconin jshttp/on-headers#19- ci: apply OSSF Scorecard security best practices by
@UlisesGasconin jshttp/on-headers#20- 👷 add upstream change detection by
@ctcpipin jshttp/on-headers#31- ✨ add script to update known hashes by
@ctcpipin jshttp/on-headers#32- 💚 update CI - add newer node versions by
@ctcpipin jshttp/on-headers#33New Contributors
@carpassemade their first contribution in jshttp/on-headers#12@UlisesGasconmade their first contribution in jshttp/on-headers#19@ctcpipmade their first contribution in jshttp/on-headers#31Full Changelog: https://github.com/jshttp/on-headers/compare/v1.0.2...v1.1.0
Commits
4b017af1.1.0b636f2d♻️ refactor header array code3e2c2d4✨ ignore falsy header keys, matching node behavior172eb41✨ support duplicate headersc6e3849🔒️ fix array handling6893518💚 update CI - add newer node versions56a345d✨ add script to update known hashes175ab21👷 add upstream change detection (#31)ce0b2c8ci: apply OSSF Scorecard security best practices (#20)1a38c54fix: useubuntu-latestas ci runner (#19)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for on-headers since your current version.
Updates path-to-regexp from 0.1.7 to 0.1.12
Release notes
Sourced from path-to-regexp's releases.
Fix backtracking (again)
Fixed
- Improved backtracking protection for 0.1.x, will break some previously valid paths (see previous advisory: https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)
https://github.com/pillarjs/path-to-regexp/compare/v0.1.11...v0.1.12
Error on bad input
Changed
- Add error on bad input values 8f09549
https://github.com/pillarjs/path-to-regexp/compare/v0.1.10...v0.1.11
Backtrack protection
Fixed
- Add backtrack protection to parameters 29b96b4
- This will break some edge cases but should improve performance
https://github.com/pillarjs/path-to-regexp/compare/v0.1.9...v0.1.10
Support non-lookahead regex output
Added
- Allow a non-lookahead regex (#312) c4272e4
Pull Request Statistics
0
0
+0
-0
Package Dependencies
@angular-devkit/build-angular
npm
17.1.3 → 20.2.2
Major
Security Advisories
path-to-regexp outputs backtracking regular expressions
cookie accepts cookie name, path, and domain with out of bounds characters
on-headers is vulnerable to http response header manipulation
Technical Details
| ID: | 7372963 |
| UUID: | 3400439279 |
| Node ID: | PR_kwDOLP6sz86ntjOP |
| Host: | GitHub |
| Repository: | batuhan-basoglu/NET-Web-API-w-Angular |