build(deps): bump the angular group in /generators/angular/resources with 3 updates

[dependabot[bot]]

Bumps the angular group in /generators/angular/resources with 3 updates: @angular/common, ngx-cookie-service and @angular/cli.

Updates @angular/common from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/common's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
  

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger

... (truncated)

Changelog

Sourced from @​angular/common's changelog.

19.0.0 (2024-11-19)

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
  

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

... (truncated)

Commits

• 7dfb127 refactor: add @__PURE__ next to @pureOrBreakMyCode for improved bundler c...
• da9c0c5 refactor: cleanup initializers that use ctor params (#58349)
• 24c6373 feat(common): add optional rounded transform support in cloudinary image load...
• 4b9accd feat(http): promote withRequestsMadeViaParent to stable. (#58221)
• 13c1306 feat(common): disable keyvalue sorting using null compareFn (#57487)
• 09df589 refactor(core): Migrate all packages with the explicit-standalone-flag sche...
• 08b4a8a docs: move JSDoc below constructor (#57187)
• a36744e docs: move JSDoc before functions (#58087)
• 0eb1c5c docs(common): Minor typo in code example (#58085)
• 84b6896 refactor(platform-server): Add an ssr benchmark setup. (#57647)
• Additional commits viewable in compare view

Updates ngx-cookie-service from 18.0.0 to 19.0.0

Release notes

Sourced from ngx-cookie-service's releases.

19.0.0

What's Changed

• feat(core): adds angular 19 support (#329) by @​pavankjadda in stevermeister/ngx-cookie-service#331

New Contributors

• @​akwiatek made their first contribution in stevermeister/ngx-cookie-service#317

Full Changelog: https://github.com/stevermeister/ngx-cookie-service/compare/v18.0.0...v19.0.0

19.0.0-rc.2

Full Changelog: https://github.com/stevermeister/ngx-cookie-service/compare/v19.0.0-next.1...v19.0.0-rc.2

19.0.0-rc.1

No release notes provided.

19.0.0-next.1

What's Changed

Full Changelog: https://github.com/stevermeister/ngx-cookie-service/compare/v18.0.0...v19.0.0-next.1

Commits

• e5a85e4 feat(core): adds angular 19 support (#329) (#331)
• e89331d Merge pull request #330 from stevermeister/development
• f442a8b chore: updates package-lock.json
• 8ec5600 Merge branch 'refs/heads/master' into development
• da9f1b1 chore(deps): bump cookie and express (#328)
• d6c916b chore(deps): bump rollup from 4.18.0 to 4.22.4 (#323)
• eb06769 chore(deps-dev): bump express from 4.19.2 to 4.21.0 (#322)
• 037e7aa Merge branch 'master' into development
• 7a26a34 chore(docs): documents angular 18 support (#317)
• b872039 chore (build): Update 1-bug-report.yaml
• Additional commits viewable in compare view

Updates @angular/cli from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/cli's releases.

v19.0.0

19.0.0 (2024-11-19)

@​angular/cli

Commit	Description
	handle string key/value pairs, e.g. --define
	recommend optional application update migration during v19 update
	enable Node.js compile code cache when available
	enable Node.js compile code cache when available

@​schematics/angular

Commit	Description
	add option to export component as default
	add option to setup new workspace or application as zoneless mode
	integrate withEventReplay() in provideClientHydration for new SSR apps
	update app-shell and ssr schematics to adopt new Server Rendering API
	component spec with export default
	don't show server routing prompt when using browser builder
	enable opt-in for new @angular/ssr feature
	explicitly set standalone:false
	remove declaration and sourceMap from default tsconfig
	use default import for express

@​angular-devkit/schematics-cli

Commit	Description
	add package manager option to blank schematic

@​angular-devkit/architect

Commit	Description
	merge object options from CLI

@​angular-devkit/build-angular

Commit	Description
	karma-coverage w/ app builder
	karma+esbuild+watch
	support karma with esbuild
	bring back style tags in browser builder
	fix --watch regression in karma
	fix hanging terminal when browser-sync is not installed
	handle basename collisions
	handle main field
	remove double-watch in karma
	serve assets
	zone.js/testing + karma + esbuild
	remove deprecated browserTarget
	remove Protractor builder and schematics

@​angular-devkit/core

Commit	Description

... (truncated)

Changelog

Sourced from @​angular/cli's changelog.

19.0.0 (2024-11-19)

Breaking Changes

@​schematics/angular

• The app-shell schematic is no longer compatible with Webpack-based builders.

@​angular-devkit/build-angular

• The browserTarget option has been removed from the DevServer and ExtractI18n builders. buildTarget is to be used instead.

• Protractor is no longer supported.

  Protractor was marked end-of-life in August 2023 (see https://protractortest.org/). Projects still relying on Protractor should consider migrating to another E2E testing framework, several support solid migration paths from Protractor.

  • https://angular.dev/tools/cli/end-to-end
  • https://blog.angular.dev/the-state-of-end-to-end-testing-with-angular-d175f751cb9c

@​angular-devkit/core

• The deprecated fileBuffer function is no longer available. Update your code to use stringToFileBuffer instead to maintain compatibility.

  Note: that this change does not affect application developers.

@​angular/build

• The @angular/localize/init polyfill will no longer be added automatically to projects. To prevent runtime issues, ensure that this polyfill is manually included in the "polyfills" section of your "angular.json" file if your application relies on Angular localization features.

@​angular/ssr

• The CommonEngine API now needs to be imported from @angular/ssr/node.

  Before

  import { CommonEngine } from '@angular/ssr';
  

  After

  import { CommonEngine } from '@angular/ssr/node';
  

@​angular-devkit/schematics-cli

Commit	Type	Description
37693c40e	feat	add package manager option to blank schematic

... (truncated)

Commits

• d622e59 release: cut the v19.0.0 release
• 86acfe0 build: update Angular packages to v19 stable
• 805379e release: cut the v19.0.0-rc.3 release
• fb05e7f fix(@​angular/ssr): use wildcard server route configuration on the '/' route w...
• 4b4e000 fix(@​schematics/angular): don't show server routing prompt when using `browse...
• 2551df5 fix(@​angular/build): fully disable component style HMR in JIT mode
• 25d928b fix(@​angular-devkit/build-angular): fix hanging terminal when browser-sync ...
• ea5ae68 fix(@​angular-devkit/build-angular): bring back style tags in browser builder
• 9e6ab1b fix(@​schematics/angular): use default import for express
• 5b009cd refactor: add ngServerMode to Webpack SSR dev server
• Additional commits viewable in compare view

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[mshima]

@dependabot unignore zone.js

[dependabot[bot]]

OK, I will stop ignoring the zone.js dependency.

[dependabot[bot]]

Looks like these dependencies are updatable in another way, so this is no longer needed.