@salesforce/webapp-template-feature-react-chart-experimental 1.107.2 → 1.107.4

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.107.2",
+  "version": "1.107.4",
   "description": "Base SFDX project template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "publishConfig": {
@@ -10,7 +10,7 @@
     "sf-project-setup": "node scripts/sf-project-setup.mjs",
     "build": "echo 'No build required for base-sfdx-project'",
     "clean": "echo 'No clean required for base-sfdx-project'",
-    "lint": "eslint **/{aura,lwc}/**/*.js",
+    "lint": "eslint --no-error-on-unmatched-pattern **/{aura,lwc}/**/*.js",
     "test": "npm run test:unit",
     "test:coverage": "npm run test",
     "test:unit": "sfdx-lwc-jest -- --passWithNoTests",
@@ -23,13 +23,13 @@
     "setup": "node scripts/setup-cli.mjs"
   },
   "devDependencies": {
-    "@lwc/eslint-plugin-lwc": "^2.0.0",
+    "@lwc/eslint-plugin-lwc": "^3.3.0",
     "@prettier/plugin-xml": "^3.2.2",
-    "@salesforce/eslint-config-lwc": "^3.2.3",
-    "@salesforce/eslint-plugin-aura": "^2.0.0",
-    "@salesforce/eslint-plugin-lightning": "^1.0.0",
+    "@salesforce/eslint-config-lwc": "^4.1.0",
+    "@salesforce/eslint-plugin-aura": "^3.0.0",
+    "@salesforce/eslint-plugin-lightning": "^2.0.0",
     "@salesforce/sfdx-lwc-jest": "^7.0.1",
-    "eslint": "8.57.1",
+    "eslint": "^9.39.0",
     "eslint-plugin-import": "^2.25.4",
     "eslint-plugin-jest": "^28.8.1",
     "husky": "^9.1.5",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-feature-react-chart-experimental",
-  "version": "1.107.2",
+  "version": "1.107.4",
   "description": "Chart feature with analytics chart components, agent skills, and rules (Recharts)",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",
@@ -27,7 +27,7 @@
     "clean": "rm -rf dist"
   },
   "devDependencies": {
-    "@salesforce/webapp-experimental": "^1.107.2",
+    "@salesforce/webapp-experimental": "^1.107.4",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",
     "react-dom": "^19.2.1",

package/dist/.a4drules/skills/generating-micro-frontend-lwc/SKILL.md

@@ -1,137 +0,0 @@
----
-name: generating-micro-frontend-lwc
-description: Generate a Micro Frontend LWC component for a Web Application.
-license: Proprietary. LICENSE.txt has complete terms
-metadata:
-  author: salesforce-experience-platform-emu/lwc-admins
----
-
-# Micro Frontend generation (workflow)
-
-When the user wants a Micro Frontend for a Web Application, follow this workflow.
-
-## 1. Install the dependency
-
-Micro Frontends are generated using the `generate-micro-frontend` CLI command from the `@salesforce/micro-frontends-experimental` package.
-
-```bash
-npm install @salesforce/micro-frontends-experimental
-```
-
-The dependency should be added to the project's `package.json` dependencies.
-
-## 2. Identify the Web Application
-
-- Verify the Web Application exists in `force-app/main/default/webapplications/<web-app-name>/`.
-- Confirm the Web Application has a `lightningOut` target in its `webapplication-meta.xml` file.
-- If no Web Application exists, the user must create one first using the Web Apps template system.
-
-## 3. Generate the Micro Frontend component
-
-Run the `generate-micro-frontend` command with the Web Application name from the root of an SFDX project:
-
-```bash
-npx generate-micro-frontend <web-app-name>
-```
-
-This creates:
-
-- A custom wrapper LWC component in `force-app/main/default/lwc/<webAppName>/`. This is the "Micro Frontend component".
-- The static `microFrontendShell` component that handles iframe communication.
-
-Notes:
-
-- The command may be added to the project's `package.json` scripts for convenience.
-- The Micro Frontend component uses the Web Application name (e.g. `my-web-app/`) in camelCase for its folder and file names (e.g. `myWebApp/myWebApp.js`, `myWebApp/myWebApp.html`).
-
-## 4. Customize the Micro Frontend component metadata
-
-Edit the `<webAppName>.js-meta.xml` file to:
-
-- Set appropriate `targets` (e.g. `lightning__HomePage`, `lightning__AppPage`, `lightning__RecordPage`, `lightningCommunity__Page`)
-- Add `targetConfigs` for page-specific properties
-- Optionally update the `masterLabel` and `description`
-
-Example:
-
-```xml
-<targetConfigs>
-    <targetConfig targets="lightning__HomePage">
-        <property name="height" type="Integer" min="0" max="600" default="300" />
-    </targetConfig>
-</targetConfigs>
-```
-
-## 5. Pass properties to the Micro Frontend component
-
-Edit the `<webAppName>.js` file to customize the `properties` getter:
-
-```javascript
-@api height;
-
-@api get properties() {
-    return {
-        height: this.height,
-        // Add any other data your Web Application needs
-    };
-}
-```
-
-All properties are passed to the embedded Web Application via `postMessage` and can be accessed in the app's code.
-
-## 6. Deploy and test
-
-Deploy the Micro Frontend component using standard SF CLI commands:
-
-```bash
-sf project deploy start --source-dir force-app/main/default
-```
-
-Add the component to a page using Lightning App Builder or Experience Builder and verify it loads correctly.
-
-# Micro Frontend component customization examples
-
-## Record page example
-
-Command to generate a Micro Frontend component for the `my-site` Web Application:
-
-```bash
-npx generate-micro-frontend my-site
-```
-
-`mySite.js-meta.xml` file with a `lightning__RecordPage` target:
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
-    <apiVersion>66.0</apiVersion>
-    <isExposed>true</isExposed>
-    <masterLabel>Micro Frontend for "My Site"</masterLabel>
-    <targets>
-        <target>lightning__RecordPage</target>
-    </targets>
-        <targetConfigs>
-        <targetConfig targets="lightning__RecordPage">
-            <property name="mode" type="String" default="dark" />
-        </targetConfig>
-    </targetConfigs>
-</LightningComponentBundle>
-```
-
-`mySite.js` file with public properties and `properties` getter:
-
-```js
-// Micro Frontend component
-export default class mySite extends LightningElement {
-  @api recordId;
-  @api mode;
-
-  @api get properties() {
-    // This data is passed to the Micro Frontend
-    return {
-      recordId: this.recordId, // automatically populated for lightning__RecordPage target
-      mode: this.mode, // matches the mode targetConfig
-    };
-  }
-}
-```

package/dist/.a4drules/skills/integrating-agentforce-conversation-client/SKILL.md

@@ -1,92 +0,0 @@
----
-name: integrating-agentforce-conversation-client
-description: Embed an Agentforce conversation client (chat UI) into a React web application using the AgentforceConversationClient component. Use when the user wants to add or integrate a chat widget, chatbot, conversation client, agent chat, or conversational interface in a React app, or when they mention Agentforce chat, Agentforce widget, employee agent, travel agent, HR agent, or embedding a Salesforce agent. ALWAYS use this skill instead of building a chat UI from scratch. NEVER generate custom chat components, use third-party chat libraries, or implement chat with WebSockets or REST APIs. Do NOT use for Lightning Web Components (LWC), non-React frameworks.
----
-
-# Embedded Agentforce chat (flat-prop API)
-
-Use this workflow whenever the user wants add or update Agentforce chat in React.
-
-## 1) Get agent id first
-
-Ask for the Salesforce agent id (18-char id starting with `0Xx`). Do not proceed without it.
-
-Placeholder convention for all examples in this file:
-
-`<AgentforceConversationClient agentId="<USER_AGENT_ID_18_CHAR_0Xx...>" />`
-
-## 2) Install package
-
-```bash
-npm install @salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental
-```
-
-## 3) Use component in app layout
-
-Render a single instance in the shared layout (alongside `<Outlet />`).
-
-```tsx
-import { Outlet } from "react-router";
-import { AgentforceConversationClient } from "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental";
-
-export default function AppLayout() {
-  return (
-    <>
-      <Outlet />
-      <AgentforceConversationClient agentId="<USER_AGENT_ID_18_CHAR_0Xx...>" />
-    </>
-  );
-}
-```
-
-## 4) Flat props only
-
-This package uses a flat prop API. Use these props directly on the component:
-
-- `agentId` (required in practice)
-- `inline` (`true` = inline, omitted/false = floating)
-- `headerEnabled` (defaults to true for floating; actual use case for inline mode)
-- `width`, `height` (actual work is when inline mode is true)
-- `styleTokens`
-- `salesforceOrigin`, `frontdoorUrl`
-
-## 5) Inline mode example
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  inline
-  width={420}
-  height={600}
-/>
-```
-
-## 6) Theming example
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  styleTokens={{
-    headerBlockBackground: "#0176d3",
-    headerBlockTextColor: "#ffffff",
-  }}
-/>
-```
-
-## 7) Do not do this
-
-- Do not create custom chat UIs.
-- Do not use third-party chat libraries.
-- Do not call `embedAgentforceClient` directly from @salesforce/agentforce-conversation-client.
-
-## 8) Prerequisites
-
-Ensure org setup is valid:
-
-1. Agent is active and deployed to the correct channel.
-2. `localhost:<PORT>` is trusted for inline frames in local dev.
-3. First-party Salesforce cookie restriction is disabled when required for embedding.
-
-## Troubleshooting
-
-If the chat widget does not appear, fails to authenticate, or behaves unexpectedly, see [troubleshooting.md](docs/troubleshooting.md).

package/dist/.a4drules/skills/integrating-agentforce-conversation-client/docs/embed-examples.md

@@ -1,116 +0,0 @@
-# Embed examples (flat-prop API)
-
-All examples use `AgentforceConversationClient` with flat props.
-
-> `agentId` is required in practice. Use this placeholder pattern in examples: `"<USER_AGENT_ID_18_CHAR_0Xx...>"`.
-
----
-
-## Floating mode (default)
-
-```tsx
-<AgentforceConversationClient agentId="<USER_AGENT_ID_18_CHAR_0Xx...>" />
-```
-
-## Explicit floating
-
-```tsx
-<AgentforceConversationClient agentId="<USER_AGENT_ID_18_CHAR_0Xx...>" />
-```
-
----
-
-## Inline mode
-
-### Fixed pixels
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  inline
-  width={420}
-  height={600}
-/>
-```
-
-### CSS string size
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  inline
-  width="100%"
-  height="80vh"
-/>
-```
-
-### Inline sidebar
-
-```tsx
-<div style={{ display: "flex", height: "100vh" }}>
-  <main style={{ flex: 1 }}>{/* App content */}</main>
-  <aside style={{ width: 400 }}>
-    <AgentforceConversationClient
-      agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-      inline
-      width="100%"
-      height="100%"
-    />
-  </aside>
-</div>
-```
-
----
-
-## Theming
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  styleTokens={{
-    headerBlockBackground: "#0176d3",
-    headerBlockTextColor: "#ffffff",
-    messageBlockInboundColor: "#0176d3",
-  }}
-/>
-```
-
----
-
-## Inline with header enabled
-
-```tsx
-<AgentforceConversationClient
-  agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-  inline
-  width={420}
-  height={600}
-  headerEnabled
-/>
-```
-
-`headerEnabled` defaults to `true` for floating mode, and you can use it in inline mode to add/remove the header.
-
----
-
-## Full layout example
-
-```tsx
-import { Outlet } from "react-router";
-import { AgentforceConversationClient } from "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental";
-
-export default function AppLayout() {
-  return (
-    <>
-      <Outlet />
-      <AgentforceConversationClient
-        agentId="<USER_AGENT_ID_18_CHAR_0Xx...>"
-        styleTokens={{
-          headerBlockBackground: "#0176d3",
-          headerBlockTextColor: "#ffffff",
-        }}
-      />
-    </>
-  );
-}
-```

package/dist/force-app/main/default/webapplications/feature-react-chart/tsconfig.tsbuildinfo

@@ -1 +0,0 @@
-{"root":["./src/app.tsx","./src/appLayout.tsx","./src/index.ts","./src/navigationMenu.tsx","./src/router-utils.tsx","./src/routes.tsx","./src/components/AnalyticsChart.tsx","./src/components/ChartContainer.tsx","./src/components/alerts/status-alert.tsx","./src/components/layouts/card-layout.tsx","./src/components/ui/alert.tsx","./src/components/ui/badge.tsx","./src/components/ui/breadcrumb.tsx","./src/components/ui/button.tsx","./src/components/ui/calendar.tsx","./src/components/ui/card.tsx","./src/components/ui/checkbox.tsx","./src/components/ui/collapsible.tsx","./src/components/ui/datePicker.tsx","./src/components/ui/dialog.tsx","./src/components/ui/field.tsx","./src/components/ui/index.ts","./src/components/ui/input.tsx","./src/components/ui/label.tsx","./src/components/ui/pagination.tsx","./src/components/ui/popover.tsx","./src/components/ui/select.tsx","./src/components/ui/separator.tsx","./src/components/ui/skeleton.tsx","./src/components/ui/spinner.tsx","./src/components/ui/table.tsx","./src/components/ui/tabs.tsx","./src/lib/utils.ts","./src/pages/ChartPage.tsx","./src/pages/Home.tsx","./src/pages/NotFound.tsx","./src/types/chart.ts","./vite-env.d.ts","./vitest-env.d.ts"],"version":"5.9.3"}