Bump http-cache-semantics, npm-check-updates and @angular/cli

[dependabot]

Bumps http-cache-semantics to 4.1.1 and updates ancestor dependencies http-cache-semantics, npm-check-updates and @angular/cli. These dependencies need to be updated together.

Updates http-cache-semantics from 3.8.1 to 4.1.1

Commits

• 2449650 Update mocha
• 560b2d8 Don't use regex to trim whitespace
• b1bdb92 Remove linting package zoo
• c20dc7e Cache 308
• ed83aec Explain trust server date
• 1b35980 rfc 5861 (stale-if-error, stale-while-revalidate)
• 2c2fac2 Drop trustServerDate
• eb7028f Test names
• 84cc9a8 Bump
• ae5ecd5 Add status to tests
• Additional commits viewable in compare view

Updates npm-check-updates from 3.1.24 to 16.10.10

Release notes

Sourced from npm-check-updates's releases.

v16.10.0

Feature

• Added filterResults option to filter out upgrades based on a user provided function.

filterResults runs after new versions are fetched, in contrast to filter and filterVersion, which run before. This allows you to filter out upgrades with filterResults based on how the version has changed (e.g. a major version change).

Only available in .ncurc.js or when importing npm-check-updates as a module.

/** Filter out non-major version updates.
  @param {string} packageName               The name of the dependency.
  @param {string} currentVersion            Current version declaration (may be range).
  @param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be range).
  @param {string} upgradedVersion           Upgraded version.
  @param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
  @returns {boolean}                        Return true if the upgrade should be kept, otherwise it will be ignored.
*/
filterResults: (packageName, {currentVersion, currentVersionSemver, upgradedVersion, upgradedVersionSemver}) => {
  const currentMajorVersion = currentVersionSemver?.[0]?.major
  const upgradedMajorVersion = upgradedVersionSemver?.major
  if (currentMajorVersion && upgradedMajorVersion) {
    return currentMajorVersion < upgradedMajorVersion
  }
  return true
}

For the SemVer type definition, see: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring

Thanks to mslowiak for this enhancement!

v16.8.0

Feature

• Added --format lines

$ ncu --format lines
@ava/typescript@^4.0.0
ava@^5.2.0
eslint@^8.36.0
lerna@^6.5.1
typescript@^5.0.2

This is particularly useful for upgrading global modules:

npm install -g $(ncu -g --format lines)
</tr></table> 

... (truncated)

Changelog

Sourced from npm-check-updates's changelog.

Changelog

This file documents all major version releases. For other releases, please read the commit history.

[16.0.0] - 2022-07-23

Breaking

• Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior.
• Wild card filters now apply to scoped packages. Previously, ncu -f '*vite*' would not include @vitejs/plugin-react. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.

raineorshine/npm-check-updates@v15.3.4...v16.0.0

[15.0.0] - 2022-06-30

Breaking

• node >= 14.14 is now required (#1145)
  • Needed to upgrade update-notifier with has a moderate severity vulnerability
• yarn autodetect has been improved (#1148)
  • This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
  • More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

raineorshine/npm-check-updates@v14.1.1...v15.0.0

[14.0.0] - 2022-06-16

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre 1 or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

• You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

[13.0.0] - 2022-05-15

Breaking

• node >= 14 is now required
• Several options which have long been deprecated have been removed:
  • --greatest - Instead use --target greatest

... (truncated)

Commits

• See full diff in compare view

Updates @angular/cli from 8.3.9 to 16.0.0

Release notes

Sourced from @​angular/cli'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/cli'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

• 95e1b40 release: cut the v16.0.0 release
• 4f0c1df refactor: bump @angular/pwa peer dependency version for v16
• c8cb641 refactor: bump peer dependencies for v16 release
• 869609c release: cut the v16.0.0-rc.4 release
• 26dced9 fix(@​angular-devkit/build-angular): JIT support for standalone applications
• 7d792b2 refactor(@​angular-devkit/build-angular): update esbuild builder option status...
• 4cc35f3 build: update all non-major dependencies
• e17dc92 release: cut the v16.0.0-rc.3 release
• 4d8de73 refactor(@​angular-devkit/build-angular): exclude `@angular/platform-server/in...
• e690b7c fix(@​angular-devkit/build-angular): always enable looseEnums build optimize...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @​angular/cli 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.