Bump webpack-subresource-integrity and @angular-devkit/build-angular

[dependabot]

Bumps webpack-subresource-integrity to 5.1.0 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.

Updates webpack-subresource-integrity from 1.3.4 to 5.1.0

Release notes

Sourced from webpack-subresource-integrity's releases.

v5.1.0

• Allow deferred loading of hashes. Specifying the new option hashLoading: "lazy" will cause integrity hashes for any given asset to be defined in its direct parents in the chunk graph. This can lead to duplication of hashes across assets, but can significantly reduce the size of entry chunk(s) when there are a large number of async chunks. (#171)

v5.0.0

No changes compared to v5.0.0-rc.1.

Changes compared to v1.5.2:

BREAKING CHANGES

(See migrating from v1 to v5.)

• Drop compatibility with Webpack < 5.12.0.
• Drop compatibility with Node < 10.
• Drop compatibility with html-webpack-plugin < 5.0.0-beta.1.
• Drop default export, new named export SubresourceIntegrityPlugin.
• When integrity for an asset cannot be determined this now emits an error. Previously, a warning was emitted.
• Option enabled now defaults to "auto", which enables the plugin in all Webpack modes except for development. Previously, the plugin was disabled by default in all modes.

Other Changes

• Compatibility with html-webpack-plugin 5 and new Webpack 5 asset processing pipeline.
• Option hashFuncNames now has a default: ["sha384"].
• All code has been rewritten in TypeScript. We now include TypeScript type definitions inside the package.
• No longer imports webpack (#150)
• Warn when using dangerous filename hashes (#162)

v5.0.0-rc.1

• Warn when using dangerous filename hashes (#162)
• Minor non-functional changes

v5.0.0-alpha.5

• Fix handling of chunks with multiple files (#154)
• Fix stats factory when using real content hash

v5.0.0-alpha.4

• Fix real content hash generation (#152)

v5.0.0-alpha.3

• Do not import webpack (#150)

  Adds compatibility with Next.js 10.0.6. Please note that installing this plugin in Next.js is not enough to gain integrity since top-level assets will remain unprotected.

v5.0.0-alpha.2

• Fix error when a processed tag has no attributes (#147)

v5.0.0-alpha.1

BREAKING CHANGES

• Drop compatibility with Webpack < 5.12.0.
• Drop compatibility with Node < 10.

... (truncated)

Commits

• ad9265e Bump to version 5.1.0
• d049da4 Lazy hashes follow-up
• fc7cf19 Add lazyHashes option to define integrity hashes only in direct parents of ...
• 3d93750 Use npm badge from default tag
• 40ec3ce Bump to version 5.0.0
• e5ccea1 Cache puppeteer download
• b20961f Add daily compatibility CI run
• f92330d Update test instructions
• 61cca07 Update homepage link
• 299be93 Clean up badges
• Additional commits viewable in compare view

Updates @angular-devkit/build-angular from 0.900.4 to 16.0.0

Release notes

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

v16.0.0

16.0.0 (2023-05-03)

@​angular/cli

Commit	Description
	remove deprecated defaultCollection from workspace configuration
	remove deprecated defaultProject from workspace configuration
	show optional migrations during update process
	remove Node.js v14 support

@​schematics/angular

Commit	Description
	add support to add service worker to standalone application
	generate functional resolvers and guards by default
	Implement a standalone flag for new applications
	remove deprecated CanLoad option for guards
	remove generation of BrowserModule.withServerTransition
	update app-shell schematic to support standalone applications
	Update universal schematic to support standalone applications
	add experimental message when using standalone application schematic.
	add standalone option to library library
	provide migration that disables build optimizer on dev server builds
	reformat app.config.ts
	remove compileComponents from component test schematic
	rename app.server.module.ts to app.module.server.ts
	replace provideServerSupport with provideServerRendering
	update private Components utilities to work with standalone project structure
	use same property order in standalone AppComponent

Commit	Description
	update to TypeScript 5 and drop support for TypeScript 4.8

@​angular-devkit/architect

Commit	Description
	allow registered builder teardowns to execute

@​angular-devkit/build-angular

Commit	Description
	add CSP support for inline styles
	display build output table with esbuild
	implement progress option for esbuild builder
	initial autoprefixer support for CSS in esbuild builder
	initial development server for esbuild-based builder
	initial tailwindcss support for CSS in esbuild builder
	support module resolution with less stylesheets in esbuild builder
	support scripts option with esbuild builder
	support SSL options with esbuild development server
	support standalone app-shell generation

... (truncated)

Changelog

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

16.0.0 (2023-05-03)

Breaking Changes

@​angular/cli

• The deprecated defaultCollection workspace option has been removed. Use schematicCollections instead.

  Before

  "defaultCollection": "@angular/material"

  After

  "schematicCollections": ["@angular/material"]

• The deprecated defaultProject workspace option has been removed. The project to use will be determined from the current working directory.

• Node.js v14 support has been removed

  Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.

@​schematics/angular

• ng g resolver and ng g guard now generate a functional resolver or guard by default. It is still possible to generate a (deprecated) class-based resolver or guard by using ng g resolver --no-functional or ng g guard --no-functional.
• The CLI no longer allows to generate CanLoad guards. Use CanMatch instead.

• • TypeScript 4.8 is no longer supported.

@​angular-devkit/build-angular

• Deprecated outputPath and outputPaths from the server and browser builder have been removed from the builder output. Use outputs instead.

  Note: this change does not effect application developers.

@​angular-devkit/core

• Several changes to the SchemaRegistry.
  • compile method now returns a Promise.
  • Deprecated flatten has been removed without replacement.
• • ContentHasMutatedException, InvalidUpdateRecordException, UnimplementedException and MergeConflictException API from @angular-devkit/core have been removed in favor of the API from @angular-devkit/schematics.
  • UnsupportedPlatformException - A custom error exception should be created instead.

@​angular-devkit/schematics

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @​angular-devkit/build-angular since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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.