@primexperts.co/pulse-agent 5.6.0 → 5.7.1

package/LICENSE

@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

package/README.md

@@ -81,7 +81,7 @@ Use these values in your widget config:
 | API base URL | `https://pulse.service.primexperts.co.za` | Yes | Use the API URL shown by your Pulse environment. |
 | Website origin | `https://www.example.com` | Required for production | Add the exact site origin where the widget will run. |
 
-You usually do not need a widget token. Pulse Agent resolves it automatically from your organization slug; when an application key is configured, the agent also sends it for app-aware deployments and reporting context.
+You usually do not need a widget token. Pulse Agent resolves it automatically from your organization slug; when an application key is configured, the agent also sends it for app-aware deployments and reporting context.
 ## Configuration Keys
 
 | Option | Type | Default | Description |
@@ -172,7 +172,7 @@ Structure your app so `createPulseAgent(...)` runs:
 
 Do not initialize Pulse Agent inside frequently re-rendered child components, route components that mount repeatedly, button click handlers, or server-only files. If the root component can unmount, keep the returned handle and call `agent.destroy()` during cleanup.
 
-For error monitoring, timing matters: errors that happen before `createPulseAgent(...)` runs cannot be captured by Pulse Agent. If you want broad coverage, load runtime config first and initialize Pulse Agent before bootstrapping the rest of the application where your framework allows it.
+For error monitoring, timing matters: errors that happen before `createPulseAgent(...)` runs cannot be captured by Pulse Agent. If you want broad coverage, load runtime config first and initialize Pulse Agent before bootstrapping the rest of the application where your framework allows it.
 ## Runtime Config Pattern
 
 A common production-safe pattern is to load `/runtime-config.js` before your app bundle:
@@ -334,7 +334,7 @@ Pulse Agent is a browser widget, so it uses standard browser networking APIs to
 - `EventSource` keeps the chat connected for realtime replies.
 - Optional `fetch` wrapping reports failed website requests only when `errorMonitoring` and `captureFetchErrors` are enabled.
 
-The package does not run install scripts, does not start background processes, does not open arbitrary sockets, and does not use Node filesystem or shell APIs at runtime. Network calls are made from the visitor's browser after the website initializes `createPulseAgent(...)`, and they target the configured `apiBaseUrl` plus optional WhatsApp links when configured.
+The package does not run install scripts, does not start background processes, does not open arbitrary sockets, and does not use Node filesystem or shell APIs at runtime. Network calls are made from the visitor's browser after the website initializes `createPulseAgent(...)`, and they target the configured `apiBaseUrl` plus optional WhatsApp links when configured.
 ## Error Monitoring
 
 Error monitoring is opt-in. Installing the package does not capture anything until `errorMonitoring: true` is passed to `createPulseAgent`.
@@ -402,8 +402,8 @@ Admin setup endpoints are separate and should remain authenticated.
 - Works with npm or a script tag.
 - Supports runtime configuration, which is useful for Heroku, Docker, static hosting, and multi-environment deployments.
 - Uses the organization `slug`, plus `appKey` when available, so users do not need to handle internal widget tokens.
-- Supports visitor profile capture, history loading, transcript email requests, SSE replies, WhatsApp launcher/contact path where configured, manual open/close, and manual exception reporting.
-- Supports operational workflows verified in the Pulse source: assignment, status/priority updates, internal notes, follow-ups, customer profiles, tags, notifications, activity logs, exports, and dashboard KPIs.
+- Supports visitor profile capture, history loading, transcript email requests, SSE replies, WhatsApp launcher/contact path where configured, manual open/close, and manual exception reporting.
+- Supports operational workflows verified in the Pulse source: assignment, status/priority updates, internal notes, follow-ups, customer profiles, tags, notifications, activity logs, exports, and dashboard KPIs.
 - Supports role-based team operation: admins manage setup and assignment, while agents work assigned conversations.
 
 ## Limitations

package/docs/IMPLEMENTATION-GUIDE.md

@@ -91,7 +91,7 @@ Pulse Agent is a browser widget, so it uses standard browser networking APIs to
 - `EventSource` keeps the chat connected for realtime replies.
 - Optional `fetch` wrapping reports failed website requests only when `errorMonitoring` and `captureFetchErrors` are enabled.
 
-The package does not run install scripts, does not start background processes, does not open arbitrary sockets, and does not use Node filesystem or shell APIs at runtime. Network calls are made from the visitor's browser after the website initializes `createPulseAgent(...)`, and they target the configured `apiBaseUrl` plus optional WhatsApp links when configured.
+The package does not run install scripts, does not start background processes, does not open arbitrary sockets, and does not use Node filesystem or shell APIs at runtime. Network calls are made from the visitor's browser after the website initializes `createPulseAgent(...)`, and they target the configured `apiBaseUrl` plus optional WhatsApp links when configured.
 ## 5. Error Monitoring Configuration
 
 Error monitoring is off by default. Enable it explicitly:
@@ -187,7 +187,7 @@ Structure your app so `createPulseAgent(...)` runs:
 
 Do not initialize Pulse Agent inside frequently re-rendered child components, route components that mount repeatedly, button click handlers, or server-only files. If the root component can unmount, keep the returned handle and call `agent.destroy()` during cleanup.
 
-For error monitoring, timing matters: errors that happen before `createPulseAgent(...)` runs cannot be captured by Pulse Agent. If you want broad coverage, load runtime config first and initialize Pulse Agent before bootstrapping the rest of the application where your framework allows it.
+For error monitoring, timing matters: errors that happen before `createPulseAgent(...)` runs cannot be captured by Pulse Agent. If you want broad coverage, load runtime config first and initialize Pulse Agent before bootstrapping the rest of the application where your framework allows it.
 ## 7. Runtime Config Setup
 
 Frontend bundles usually cannot read platform environment variables directly at runtime. Use a runtime config file generated from environment variables.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@primexperts.co/pulse-agent",
-  "version": "5.6.0",
+  "version": "5.7.1",
   "description": "Embeddable Pulse floating chat agent widget.",
   "type": "module",
   "main": "./dist/index.js",
@@ -44,5 +44,25 @@
   "dependencies": {},
   "devDependencies": {
     "typescript": "~5.8.2"
+  },
+  "homepage": "https://github.com/SS-Experts/pulse-agent#readme",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/SS-Experts/pulse-agent.git"
+  },
+  "bugs": {
+    "url": "https://github.com/SS-Experts/pulse-agent/issues"
+  },
+  "keywords": [
+    "pulse",
+    "chat",
+    "support",
+    "widget",
+    "webchat",
+    "error-monitoring",
+    "browser"
+  ],
+  "engines": {
+    "node": ">=18"
   }
 }