Bump webpack-dev-middleware and @angular-devkit/build-angular

[dependabot]

Bumps webpack-dev-middleware to 5.3.4 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.

Updates webpack-dev-middleware from 5.3.3 to 5.3.4

Release notes

Sourced from webpack-dev-middleware's releases.

v5.3.4

5.3.4 (2024-03-20)

Bug Fixes

• security: do not allow to read files above (#1779) (189c4ac)

Changelog

Sourced from webpack-dev-middleware's changelog.

5.3.4 (2024-03-20)

Bug Fixes

• security: do not allow to read files above (#1779) (189c4ac)

Commits

• 86071ea chore(release): 5.3.4
• 189c4ac fix(security): do not allow to read files above (#1779)
• See full diff in compare view

Updates @angular-devkit/build-angular from 14.2.10 to 18.0.1

Release notes

Sourced from @​angular-devkit/build-angular's releases.

v18.0.1

18.0.1 (2024-05-23)

@​schematics/angular

Commit	Description
	use angular.dev in readme

@​angular/build

Commit	Description
	avoid rebasing URLs with function calls
	disable persistent disk caching inside webcontainers by default
	handle esbuild-browser polyfills option as string during ng serve
	only import persistent cache store with active caching

v18.0.0

18.0.0 (2024-05-22)

@​schematics/angular

Commit	Description
	allow application migration to use new build package in projects where possible
	replace assets with public directory
	use eventCoalescing option by default (standalone bootstrap)
	use ngZoneEventCoalescing option by default (module bootstrap)
	use TypeScript bundler module resolution for new projects
	add less dependency in application migration if needed
	add postcss dependency in application migration if needed
	add spaces around eventCoalescing option
	keep deployUrl option when migrating to application builder

@​angular/cli

Commit	Description
	add ng dev alias to ng serve
	support for Node.js v22
	add --version option
	add @angular/build package to update group list
	change update guide link to angular.dev
	eliminate prompts during ng version command
	keep cli package first in update package group metadata
	only add --version option on default command
	remove ng doc command
	remove support for Node.js versions <18.19.1 and <20.11.1

@​angular-devkit/architect

Commit	Description
	resolve builder aliases from containing package

@​angular-devkit/build-angular

Commit	Description

... (truncated)

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

18.0.1 (2024-05-23)

@​schematics/angular

Commit	Type	Description
01842f515	fix	use angular.dev in readme

@​angular/build

Commit	Type	Description
7d253e9cd	fix	avoid rebasing URLs with function calls
6b6a76a99	fix	disable persistent disk caching inside webcontainers by default
ba70a50b6	fix	handle esbuild-browser polyfills option as string during ng serve
706423aca	fix	only import persistent cache store with active caching

18.0.0 (2024-05-22)

Breaking Changes

@​angular/cli

• The ng doc command has been removed without a replacement. To perform searches, please visit www.angular.dev
• Node.js support for versions <18.19.1 and <20.11.1 has been removed.

@​angular-devkit/build-angular

• By default, the index.html file is no longer emitted in the browser directory when using the application builder with SSR. Instead, an index.csr.html file is emitted. This change is implemented because in many cases server and cloud providers incorrectly treat the index.html file as a statically generated page. If you still require the old behavior, you can use the index option to specify the output file name.

  "architect": {
    "build": {
      "builder": "@angular-devkit/build-angular:application",
      "options": {
        "outputPath": "dist/my-app",
        "index": {
          "input": "src/index.html",
          "output": "index.html"
        }
      }
    }
  }

• The support for the legacy Sass build pipeline, previously accessible via NG_BUILD_LEGACY_SASS when utilizing webpack-based builders, has been removed.

... (truncated)

Commits

• 9e9ca22 release: cut the v18.0.1 release
• 6b6a76a fix(@​angular/build): disable persistent disk caching inside webcontainers by ...
• 01842f5 fix(@​schematics/angular): use angular.dev in readme
• ba70a50 fix(@​angular/build): handle esbuild-browser polyfills option as string du...
• 7d253e9 fix(@​angular/build): avoid rebasing URLs with function calls
• 706423a fix(@​angular/build): only import persistent cache store with active caching
• 2dbe21f release: cut the v18.0.0 release
• 2320352 build: update Angular packages to v18 stable
• dd786d4 fix(@​angular/cli): only add --version option on default command
• 2aeecd6 release: cut the v18.0.0-rc.3 release
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.