wacom 21.2.5 → 21.2.7

package/README.md

@@ -2,6 +2,8 @@
 
 Module which has common services, pipes, directives and interfaces which can be used on all projects.
 
+Wacom is SSR-safe and works with Angular Universal: browser-only APIs are guarded, and features that require a browser runtime activate only on the client.
+
 ## License
 
 [MIT](LICENSE)
@@ -66,7 +68,7 @@ export const appConfig = {
 | [**`RTC`**](https://www.npmjs.com/package/wacom#rtc-service)         |        Wraps WebRTC peer connections and local media streams        |
 | [**`Util`**](https://www.npmjs.com/package/wacom#util-service)       |      Utility methods for forms, validation, and CSS variables       |
 | [**`Theme`**](#theme-service)                                        |       Manages UI theme mode, density, and radius preferences        |
-| [**`Translate`**](#translate-service)                                |        Lightweight, signal-based runtime translate engine           |
+| [**`Translate`**](#translate-service)                                |         Lightweight, signal-based runtime translate engine          |
 
 ## [Core Service](#core-service)
 
@@ -2144,7 +2146,7 @@ ngOnInit() {
 }
 ```
 
-## [Translate Service](#translate-service)
+## [Translate Service](#translate-service)
 
 Wacom includes a lightweight, signal-based runtime translation engine built for Angular Signals.
 
@@ -2160,13 +2162,13 @@ Unlike compile-time Angular i18n, this works fully at runtime.
 
 ---
 
-### Translate model
+### Translate model
 
 ```ts
-export interface Translate {
-	sourceText: string;
-	text: string;
-}
+export interface Translate {
+	sourceText: string;
+	text: string;
+}
 ```
 
 Each `sourceText` acts as both:
@@ -2179,11 +2181,11 @@ Each `sourceText` acts as both:
 ### Basic usage (signal API)
 
 ```ts
-import { TranslateService } from "wacom";
-
-private _translateService = inject(TranslateService);
-
-title = this._translateService.translate("Create project");
+import { TranslateService } from "wacom";
+
+private _translateService = inject(TranslateService);
+
+title = this._translateService.translate("Create project");
 ```
 
 The returned value is a `WritableSignal<string>`.
@@ -2201,7 +2203,7 @@ automatically.
 ### Updating translations in bulk (language switch)
 
 ```ts
-this._translateService.setMany([
+this._translateService.setMany([
 	{ sourceText: 'Create project', text: 'Створити проєкт' },
 	{ sourceText: 'Save', text: 'Зберегти' },
 ]);
@@ -2218,7 +2220,7 @@ Behavior:
 ### Updating a single translation
 
 ```ts
-this._translateService.setOne({
+this._translateService.setOne({
 	sourceText: 'Save',
 	text: 'Зберегти',
 });
@@ -2263,9 +2265,31 @@ Optional explicit key:
 
 ### Persistence
 
-Translate entries are automatically:
+Translate entries are automatically:
 
 - hydrated from storage on startup
 - synced after every update
 
 No extra config required.
+
+## AGENTS.md
+
+Copy below code into AGENTS.md file of your project while you are using our plugin.
+
+```md
+- This project uses `wacom`, an Angular utility library for shared services, directives, pipes, and app-level configuration.
+- Prefer bootstrapping with `provideWacom({...})` in application providers. Use `WacomModule` / `WacomModule.forRoot()` only for legacy NgModule-based apps.
+- Put library-wide configuration in `provideWacom()` instead of scattering it across components. Available config areas include `http`, `store`, `meta`, `network`, and optional `socket` / `io`.
+- Prefer the library services before adding duplicate app utilities:
+  - `HttpService` for API calls and shared headers/base URL handling.
+  - `StoreService` for persisted local storage values.
+  - `MetaService` for title, description, robots, image, and link tags.
+  - `CrudService` for data flows that need offline-aware syncing behavior.
+  - `EmitterService`, `NetworkService`, `SocketService`, `RtcService`, `TimeService`, and `UtilService` when their built-in behavior matches the need.
+- Prefer importing the specific Wacom directives, pipes, and translation helpers you need instead of wrapping the whole library again in another shared abstraction.
+- For metadata, prefer configuring defaults in `provideWacom({ meta: ... })` and using `MetaService` or route metadata. If route-driven updates are expected, prefer `meta.applyFromRoutes = true`; use `MetaGuard` only when that flow specifically needs a guard.
+- For translations, register app translations with `provideTranslate(...)` and use the exported translation pipe/directive rather than creating another parallel translation bootstrap path.
+- Keep SSR-safe behavior intact. Do not add unguarded direct access to browser-only globals such as `window`, `document`, storage, media devices, or WebRTC APIs when Wacom already provides a guarded service for that area.
+- When changing app behavior, prefer configuring or composing Wacom services first before modifying the library source.
+- Common reusable building blocks exported by the library include `clickOutside`, manual form-related directives, translation helpers, and array/search/safe/pagination-style pipes.
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wacom",
-  "version": "21.2.5",
+  "version": "21.2.7",
   "license": "MIT",
   "repository": "WebArtWork/wacom",
   "funding": [