Bump @ngx-pwa/local-storage from 20.0.1 to 21.0.0 in /client

[dependabot]

Bumps @ngx-pwa/local-storage from 20.0.1 to 21.0.0.

Release notes

Sourced from @​ngx-pwa/local-storage's releases.

v21.0.0

Breaking changes

Angular 21 is required.

Changelog

Sourced from @​ngx-pwa/local-storage's changelog.

21.0.0 (2025-11-20)

Breaking changes

• Angular 21 is required.

20.0.0 (2025-05-29)

Breaking changes

• Angular 20 is required.

19.0.0 (2024-11-19)

Breaking changes

• Angular 19 is required.
• RxJS >= 7.6 is required. RxJS 6 is not supported.

18.0.0 (2024-05-22)

Breaking changes

• Angular 18 is required.
• RxJS >= 7.6 is required. RxJS 6 is not supported.
• Made internal properties and methods of StorageMap natively private (#property) instead of protected. Extending StorageMap was undocumented so it is not considered a breaking change.

17.0.0 (2023-11-08)

Breaking changes

• Angular 17 is required.
• RxJS >= 7.4 is required. RxJS 6 is not supported.
• All things deprecated in v16 are removed in v17:
  • LocalStorage service
  • specific JSONSchemaXXX interfaces
  • JSONValidator
  • LocalDatabase

See the migration guide.

16.3.0 (2023-06-04)

• Specific JSONSchemaXXX interfaces are deprecated and will be removed in version 17. They were introduced in very old versions of this library as a workaround to some TypeScript issues which are gone for a long time now. Since version 8, you should have used the generic JSONSchema interface. Note that if you are using JSONSchemaArray for a tuple schema, you need to switch to JSONSchema now because of the fix in version 16.2.0.

• JSONValidator is deprecated and will no longer be available in version 17. It is an internal utility class which is limited, could change at any time and is out of scope of this library. If you need a JSON validator, there are far better and dedicated libraries available like ajv.

• LocalDatabase is deprecated and will no longer be available in version 17. It is an internal utility class, and overriding it is an undocumented behavior. If you are doing so, you are basically rewriting your own storage library, so using this one makes no sense, you can your service directly.

16.2.0 (2023-06-04)

... (truncated)

Commits

• 32b93c9 21.0.0
• 8054bbf release
• 1475530 Merge pull request #1024 from cyrilletuzi:ng21
• c1e180f node 24 in ci
• fe3abea version update
• 688f8bd remove zone
• 5cee39a remove zone from tests apps
• b971af1 align angular config
• 5897dc9 add packageManager config
• 50608b7 align gitignore
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)