22.0.0

22.0.0 (2026-06-19)

Features

• solace-message-client: add support for Angular 22 (18e408c)

BREAKING CHANGES

• solace-message-client: Angular Solace Message Client requires Angular 22.

21.1.0

21.1.0 (2026-05-22)

Bug Fixes

• tryme: prevent error on empty message content (ee1fb9c)

Features

• solace-message-client: provide support for zoneless change detection (596a5d7)

21.0.0

21.0.0 (2025-11-24)

Features

• solace-message-client: add support for Angular 21 (ff4a014)

BREAKING CHANGES

• solace-message-client: Angular Solace Message Client requires Angular 21.
  Note that Angular Solace Message Client does not support zoneless mode and may not work as expected. Support is planned for 2026.

• solace-message-client: Angular Solace Message Client now requires @scion/toolkit version 2.0.0 or higher.
  For more information, refer to the changelog of @scion/toolkit: https://github.com/SchweizerischeBundesbahnen/scion-toolkit/blob/master/CHANGELOG_TOOLKIT.md.

20.0.0

20.0.0 (2025-06-11)

Features

• solace-message-client: add support for Angular 20 (030314f)

Code Refactoring

• solace-message-client: remove deprecated API to manually connect and disconnect from the broker (9a5b814), closes #70

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 20 introduced a breaking change.
  To migrate:

  • Update your application to Angular 20. For detailed migration instructions, refer to Angular's update guide: https://v20.angular.dev/update-guide.
  • Remove @types/events, @types/node, and long from the dependencies in your package.json as not required anymore (since solclientjs version 10.16.0)
  • Remove node from the types array in your tsconfig as not required anymore (since solclientjs version 10.16.0)

• solace-message-client: Angular Solace Message Client now requires @scion/toolkit version 1.6.0 or higher.
  For more information, refer to the changelog of @scion/toolkit: https://github.com/SchweizerischeBundesbahnen/scion-toolkit/blob/master/CHANGELOG_TOOLKIT.md.

• solace-message-client: Angular Solace Message Client now requires solclientjs version 10.18.0 or higher.
  For more information, refer to the changelog of solclientjs: https://products.solace.com/download/JS_API_RN.

• solace-message-client: provideSolaceMessageClient now requires a config. Previously, no config was required if the app connected manually to the broker using the removed connect method.

• solace-message-client: Removed deprecated connect and disconnect methods of SolaceMessageClient.
  Initially, they allowed for a flexible configuration of the message client, which can now be done via a config function or separate environments.

  To migrate, pass a config to provideSolaceMessageClient, either as an object literal or via a function. The function can call inject to get any required dependencies and return the configuration synchronously or asynchronously, for example, to load it over the network.

  Example for loading config asynchronously:

  import {provideSolaceMessageClient} from '@solace-community/angular-solace-message-client';
  import {bootstrapApplication} from '@angular/platform-browser';
  import {HttpClient, provideHttpClient} from '@angular/common/http';
  import {inject} from '@angular/core';
  
  bootstrapApplication(AppComponent, {
    providers: [
      provideHttpClient(),
      provideSolaceMessageClient(() => inject(HttpClient).get('path/to/config')),
    ],
  });

  A connection to the broker is established when the SolaceMessageClient is injected for the first time. To manually connect to a broker, create an environment. Different environments can be used to connect to different brokers.

  Example for manually connecting to the broker:

  import {provideSolaceMessageClient, SolaceMessageClient} from '@solace-community/angular-solace-message-client';
  import {createEnvironmentInjector, EnvironmentInjector, inject} from '@angular/core';
  
  // Configure the broker.
  const environment = createEnvironmentInjector(
    [provideSolaceMessageClient({url: 'wss://broker-url'})],
    inject(EnvironmentInjector),
  );
  
  // Connect to the broker by injecting `SolaceMessageClient`.
  const messageClient = environment.get(SolaceMessageClient);
  
  // Interact with the broker.
  messageClient.publish('topic', 'message');
  
  // Destroy the environment, disconnecting from the message broker.
  environment.destroy();

19.0.0

19.0.0 (2024-12-05)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 19 (e623821)

Chore

• solace-message-client: remove deprecated APIs (393c003)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 19 introduced a breaking change.

  To migrate:

  • Update your application to Angular 19; for detailed migration instructions, refer to https://v19.angular.dev/update-guide;
  • Update solclientjs to version 10.17.1.

• solace-message-client: Removing the deprecated APIs introduced breaking changes.

  The following APIs have been removed:

  • SolaceMessageClientModule.forRoot => register Angular Solace Message Client using provideSolaceMessageClient function instead;
  • SolaceMessageClientModule.forChild => register Angular Solace Message Client using provideSolaceMessageClient function instead;
  • OAuthAccessTokenProvider => use OAuthAccessTokenFn instead;
  • BrowseOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • ConsumeOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • ObserveOptions.emitOutsideAngularZone => messages are received in the zone in which subscribed to the Observable. To receive messages outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;
  • RequestOptions.emitOutsideAngularZone => replies are received in the zone in which subscribed to the Observable. To receive replies outside the Angular zone, subscribe to the Observable outside the Angular zone, otherwise inside the Angular zone;

18.0.0

18.0.0 (2024-06-03)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 18 (bacf6aa)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 18 introduced a breaking change.

  To migrate:

  • Update your application to Angular 18; for detailed migration instructions, refer to https://v18.angular.dev/update-guide;
  • Update solclientjs to version 10.16.0;

17.1.0

17.1.0 (2024-05-14)

Features

• solace-message-client: deprecate class-based access token provider in favor of functional access token provider (94a3f0e)
• solace-message-client: provide function to set up Solace Message Client (d9be295)
• solace-message-client: receive messages in the zone in which subscribed for messages (944b10c)
• solace-message-client: support connecting to multiple Solace message brokers (c832b00), closes #71
• solace-message-client: support loading config asynchronously (1be10e6)

17.0.1

17.0.1 (2024-05-07)

Bug Fixes

• solace-message-client: support subscriptions with #share and #noexport (fa161bc)

17.0.0

17.0.0 (2023-11-21)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 17 (49b8c86), closes #68

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 17 introduced a breaking change.

  To migrate:

  • Update your application to Angular 17; for detailed migration instructions, refer to https://v17.angular.io/guide/update-to-latest-version;
  • Update solclientjs to version 10.15.0;
  • solclientjs now requires type definitions for node. In your tsconfig, add node to the types array in compilerOptions. If you have not specified types, no manual registration of node is required, since without types array all @types packages are included in the build.

16.0.0

16.0.0 (2023-05-17)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 16 (73a5edc), closes #60

Features

• testapp: improve accessibility of testing app (7f91a5c)

BREAKING CHANGES

• solace-message-client: Updating @solace-community/angular-solace-message-client to Angular 16 introduced a breaking change.

  To migrate:

  • update your application to Angular 16; for detailed migration instructions, refer to https://v16.angular.io/guide/update-to-latest-version;
  • update solclientjs to version 10.13.0;