fjodor-rybakov / discord-nestjs

👾 NestJS package for discord.js
MIT License
271 stars 49 forks source link

chore(deps): Bump @angular-devkit/core from 15.2.7 to 16.0.0 #1067

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @angular-devkit/core from 15.2.7 to 16.0.0.

Release notes

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

v16.0.0

16.0.0 (2023-05-03)

@​angular/cli

Commit Description
feat - 68024234e remove deprecated defaultCollection from workspace configuration
feat - d58428d3d remove deprecated defaultProject from workspace configuration
feat - 7cb5689e0 show optional migrations during update process
refactor - c29c8e18d remove Node.js v14 support

@​schematics/angular

Commit Description
feat - c2d2da41b add support to add service worker to standalone application
feat - 22fdd7da9 generate functional resolvers and guards by default
feat - a832c2028 Implement a standalone flag for new applications
feat - 5ceedcb11 remove deprecated CanLoad option for guards
feat - c9e84d024 remove generation of BrowserModule.withServerTransition
feat - 50b9e59a5 update app-shell schematic to support standalone applications
feat - dc5cc893d Update universal schematic to support standalone applications
fix - f98c9de80 add experimental message when using standalone application schematic.
fix - a5cb46124 add standalone option to library library
fix - b2ed7bd10 provide migration that disables build optimizer on dev server builds
fix - ba4414b2c reformat app.config.ts
fix - 202e9a50f remove compileComponents from component test schematic
fix - 0d58f73c5 rename app.server.module.ts to app.module.server.ts
fix - de6d30102 replace provideServerSupport with provideServerRendering
fix - bff634fe0 update private Components utilities to work with standalone project structure
fix - 85fe820b0 use same property order in standalone AppComponent

Commit Description
build - 5a171ddff update to TypeScript 5 and drop support for TypeScript 4.8

@​angular-devkit/architect

Commit Description
fix - 48871381a allow registered builder teardowns to execute

@​angular-devkit/build-angular

Commit Description
feat - ff5ebf9b1 add CSP support for inline styles
feat - ee8013f66 display build output table with esbuild
feat - 0eac98f61 implement progress option for esbuild builder
feat - f04859d16 initial autoprefixer support for CSS in esbuild builder
feat - 8c550302c initial development server for esbuild-based builder
feat - 52969db6b initial tailwindcss support for CSS in esbuild builder
feat - ce46ecae0 support module resolution with less stylesheets in esbuild builder
feat - 584b51907 support scripts option with esbuild builder
feat - e4883b0ee support SSL options with esbuild development server
feat - 290802060 support standalone app-shell generation

... (truncated)

Changelog

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


Dependabot compatibility score

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)
dependabot[bot] commented 1 year ago

Superseded by #1072.