@salesforce/webapp-template-app-react-sample-b2x-experimental 1.92.1 → 1.93.0

package/dist/.a4drules/skills/feature-react-file-upload-file-upload/SKILL.md

@@ -0,0 +1,396 @@
+---
+name: feature-react-file-upload-file-upload
+description: Add file upload functionality to React webapps with progress tracking and Salesforce ContentVersion integration. Use when the user wants to upload files, attach documents, handle file input, create file dropzones, track upload progress, or link files to Salesforce records. This feature provides programmatic APIs ONLY — no components or hooks are exported. Build your own custom UI using the upload() API. ALWAYS use this feature instead of building file upload from scratch with FormData or XHR.
+---
+
+# File Upload API (workflow)
+
+When the user wants file upload functionality in a React webapp, follow this workflow. This feature provides **APIs only** — you must build the UI components yourself using the provided APIs.
+
+## CRITICAL: This is an API-only package
+
+The package exports **programmatic APIs**, not React components or hooks. You will:
+
+- Use the `upload()` function to handle file uploads with progress tracking
+- Build your own custom UI (file input, dropzone, progress bars, etc.)
+- Track upload progress through the `onProgress` callback
+
+**Do NOT:**
+
+- Expect pre-built components like `<FileUpload />` — they are not exported
+- Try to import React hooks like `useFileUpload` — they are not exported
+- Look for dropzone components — they are not exported
+
+The source code contains reference components for demonstration, but they are **not available** as imports. Use them as examples to build your own UI.
+
+## 1. Install the package
+
+```bash
+npm install @salesforce/webapp-template-feature-react-file-upload-experimental
+```
+
+Dependencies are automatically installed:
+
+- `@salesforce/webapp-experimental` (API client)
+- `@salesforce/sdk-data` (data SDK)
+
+## 2. Understand the three upload patterns
+
+### Pattern A: Basic upload (no record linking)
+
+Upload files to Salesforce and get back `contentBodyId` for each file. No ContentVersion record is created.
+
+**When to use:**
+
+- User wants to upload files first, then create/link them to a record later
+- Building a multi-step form where the record doesn't exist yet
+- Deferred record linking scenarios
+
+```tsx
+import { upload } from "@salesforce/webapp-template-feature-react-file-upload-experimental";
+
+const results = await upload({
+  files: [file1, file2],
+  onProgress: (progress) => {
+    console.log(`${progress.fileName}: ${progress.status} - ${progress.progress}%`);
+  },
+});
+
+// results[0].contentBodyId: "069..." (always available)
+// results[0].contentVersionId: undefined (no record linked)
+```
+
+### Pattern B: Upload with immediate record linking
+
+Upload files and immediately link them to an existing Salesforce record by creating ContentVersion records.
+
+**When to use:**
+
+- Record already exists (Account, Opportunity, Case, etc.)
+- User wants files immediately attached to the record
+- Direct upload-and-attach scenarios
+
+```tsx
+import { upload } from "@salesforce/webapp-template-feature-react-file-upload-experimental";
+
+const results = await upload({
+  files: [file1, file2],
+  recordId: "001xx000000yyyy", // Existing record ID
+  onProgress: (progress) => {
+    console.log(`${progress.fileName}: ${progress.status} - ${progress.progress}%`);
+  },
+});
+
+// results[0].contentBodyId: "069..." (always available)
+// results[0].contentVersionId: "068..." (linked to record)
+```
+
+### Pattern C: Deferred record linking (record creation flow)
+
+Upload files without a record, then link them after the record is created.
+
+**When to use:**
+
+- Building a "create record with attachments" form
+- Record doesn't exist until form submission
+- Need to upload files before knowing the final record ID
+
+```tsx
+import {
+  upload,
+  createContentVersion,
+} from "@salesforce/webapp-template-feature-react-file-upload-experimental";
+
+// Step 1: Upload files (no recordId)
+const uploadResults = await upload({
+  files: [file1, file2],
+  onProgress: (progress) => console.log(progress),
+});
+
+// Step 2: Create the record
+const newRecordId = await createRecord(formData);
+
+// Step 3: Link uploaded files to the new record
+for (const file of uploadResults) {
+  const contentVersionId = await createContentVersion(
+    new File([""], file.fileName),
+    file.contentBodyId,
+    newRecordId,
+  );
+}
+```
+
+## 3. Build your custom UI
+
+The package provides the backend — you build the frontend. Here's a minimal example:
+
+```tsx
+import {
+  upload,
+  type FileUploadProgress,
+} from "@salesforce/webapp-template-feature-react-file-upload-experimental";
+import { useState } from "react";
+
+function CustomFileUpload({ recordId }: { recordId?: string }) {
+  const [progress, setProgress] = useState<Map<string, FileUploadProgress>>(new Map());
+
+  const handleFileSelect = async (event: React.ChangeEvent<HTMLInputElement>) => {
+    const files = Array.from(event.target.files || []);
+
+    await upload({
+      files,
+      recordId,
+      onProgress: (fileProgress) => {
+        setProgress((prev) => new Map(prev).set(fileProgress.fileName, fileProgress));
+      },
+    });
+  };
+
+  return (
+    <div>
+      <input type="file" multiple onChange={handleFileSelect} />
+
+      {Array.from(progress.entries()).map(([fileName, fileProgress]) => (
+        <div key={fileName}>
+          {fileName}: {fileProgress.status} - {fileProgress.progress}%
+          {fileProgress.error && <span>Error: {fileProgress.error}</span>}
+        </div>
+      ))}
+    </div>
+  );
+}
+```
+
+## 4. Track upload progress
+
+The `onProgress` callback fires multiple times for each file as it moves through stages:
+
+| Status         | When                                           | Progress Value       |
+| -------------- | ---------------------------------------------- | -------------------- |
+| `"pending"`    | File queued for upload                         | `0`                  |
+| `"uploading"`  | Upload in progress (XHR)                       | `0-100` (percentage) |
+| `"processing"` | Creating ContentVersion (if recordId provided) | `0`                  |
+| `"success"`    | Upload complete                                | `100`                |
+| `"error"`      | Upload failed                                  | `0`                  |
+
+**Always provide visual feedback:**
+
+- Show file name
+- Display current status
+- Render progress bar for "uploading" status
+- Show error message if status is "error"
+
+## 5. Cancel uploads (optional)
+
+Use an `AbortController` to allow users to cancel uploads:
+
+```tsx
+const abortController = new AbortController();
+
+const handleUpload = async (files: File[]) => {
+  try {
+    await upload({
+      files,
+      signal: abortController.signal,
+      onProgress: (progress) => console.log(progress),
+    });
+  } catch (error) {
+    console.error("Upload cancelled or failed:", error);
+  }
+};
+
+const cancelUpload = () => {
+  abortController.abort();
+};
+```
+
+## 6. Link to current user (special case)
+
+If the user wants to upload files to their own profile or personal library:
+
+```tsx
+import {
+  upload,
+  getCurrentUserId,
+} from "@salesforce/webapp-template-feature-react-file-upload-experimental";
+
+const userId = await getCurrentUserId();
+await upload({ files, recordId: userId });
+```
+
+## API Reference
+
+### upload(options)
+
+Main upload API that handles complete flow with progress tracking.
+
+```typescript
+interface UploadOptions {
+  files: File[];
+  recordId?: string | null; // If provided, creates ContentVersion
+  onProgress?: (progress: FileUploadProgress) => void;
+  signal?: AbortSignal; // Optional cancellation
+}
+
+interface FileUploadProgress {
+  fileName: string;
+  status: "pending" | "uploading" | "processing" | "success" | "error";
+  progress: number; // 0-100 for uploading, 0 for other states
+  error?: string;
+}
+
+interface FileUploadResult {
+  fileName: string;
+  size: number;
+  contentBodyId: string; // Always available
+  contentVersionId?: string; // Only if recordId was provided
+}
+```
+
+**Returns:** `Promise<FileUploadResult[]>`
+
+### createContentVersion(file, contentBodyId, recordId)
+
+Manually create a ContentVersion record from a previously uploaded file.
+
+```typescript
+async function createContentVersion(
+  file: File,
+  contentBodyId: string,
+  recordId: string,
+): Promise<string | undefined>;
+```
+
+**Parameters:**
+
+- `file` — File object (used for metadata like name)
+- `contentBodyId` — ContentBody ID from previous upload
+- `recordId` — Record ID for FirstPublishLocationId
+
+**Returns:** ContentVersion ID if successful
+
+### getCurrentUserId()
+
+Get the current user's Salesforce ID.
+
+```typescript
+async function getCurrentUserId(): Promise<string>;
+```
+
+**Returns:** Current user ID
+
+## Common UI patterns
+
+### File input with button
+
+```tsx
+<input type="file" multiple accept=".pdf,.doc,.docx,.jpg,.png" onChange={handleFileSelect} />
+```
+
+### Drag-and-drop zone
+
+Build your own dropzone using native events:
+
+```tsx
+function DropZone({ onDrop }: { onDrop: (files: File[]) => void }) {
+  const handleDrop = (e: React.DragEvent) => {
+    e.preventDefault();
+    const files = Array.from(e.dataTransfer.files);
+    onDrop(files);
+  };
+
+  return (
+    <div
+      onDrop={handleDrop}
+      onDragOver={(e) => e.preventDefault()}
+      style={{ border: "2px dashed #ccc", padding: "2rem" }}
+    >
+      Drop files here
+    </div>
+  );
+}
+```
+
+### Progress bar
+
+```tsx
+{
+  progress.status === "uploading" && (
+    <div style={{ width: "100%", background: "#eee" }}>
+      <div
+        style={{
+          width: `${progress.progress}%`,
+          background: "#0176d3",
+          height: "8px",
+        }}
+      />
+    </div>
+  );
+}
+```
+
+## Decision tree for agents
+
+**User asks for file upload functionality:**
+
+1. **Ask about record context:**
+   - "Do you want to link uploaded files to a specific record, or upload them first and link later?"
+
+2. **Based on response:**
+   - **Link to existing record** → Use Pattern B with `recordId`
+   - **Upload first, link later** → Use Pattern A (no recordId), then Pattern C for linking
+   - **Link to current user** → Use Pattern B with `getCurrentUserId()`
+
+3. **Build the UI:**
+   - Create file input or dropzone (not provided by package)
+   - Add progress display for each file (status + progress bar)
+   - Handle errors in the UI
+
+4. **Test the implementation:**
+   - Verify progress callbacks fire correctly
+   - Check that `contentBodyId` is returned
+   - If `recordId` was provided, verify `contentVersionId` is returned
+
+## Reference implementation
+
+The package includes a reference implementation in `src/features/fileupload/` with:
+
+- `FileUpload.tsx` — Complete component with dropzone and dialog
+- `FileUploadDialog.tsx` — Progress tracking dialog
+- `FileUploadDropZone.tsx` — Drag-and-drop zone
+- `useFileUpload.ts` — React hook for state management
+
+**These are NOT exported** but can be viewed as examples. Read the source files to understand patterns for building your own UI.
+
+## Troubleshooting
+
+**Upload fails with CORS error:**
+
+- Ensure the webapp is properly deployed to Salesforce or running on `localhost`
+- Check that the org allows the origin in CORS settings
+
+**No progress updates:**
+
+- Verify `onProgress` callback is provided
+- Check that the callback function updates React state correctly
+
+**ContentVersion not created:**
+
+- Verify `recordId` is provided to `upload()` function
+- Check that the record ID is valid and exists in the org
+- Ensure user has permissions to create ContentVersion records
+
+**Files upload but don't appear in record:**
+
+- Verify `recordId` is correct
+- Check that ContentVersion was created (look for `contentVersionId` in results)
+- Confirm user has access to view files on the record
+
+## DO NOT do these things
+
+- ❌ Build XHR/fetch upload logic from scratch — use the `upload()` API
+- ❌ Try to import `<FileUpload />` component — it's not exported
+- ❌ Try to import `useFileUpload` hook — it's not exported
+- ❌ Use third-party file upload libraries when this feature exists
+- ❌ Skip progress tracking — always provide user feedback
+- ❌ Ignore errors — always handle and display error messages

package/dist/.a4drules/webapp-cli-commands.md

@@ -0,0 +1,88 @@
+---
+description: CLI command generation rules — no node -e one-liners; safe quoting and scripts
+paths:
+  - "**/webapplications/**/*"
+---
+
+# A4D Enforcement: CLI Command Generation & No `node -e` One-Liners
+
+When **generating any CLI/shell commands** (for the user or for automation), follow the rules below. Default shell is **Zsh** (macOS); commands must work there without Bash-only syntax.
+
+---
+
+## 1. Never Use Complex `node -e` One-Liners
+
+**Forbidden:** `node -e` (or `node -p`, `node --eval`) for file manipulation, string replacement, reading/writing configs, or multi-line logic.
+
+**Why:** In Zsh, `node -e '...'` **silently breaks** due to:
+- **`!` (history expansion):** Zsh expands `!` in double-quoted strings → `event not found` or wrong output.
+- **Backticks:** `` ` `` is command substitution; the shell runs it before Node sees the string.
+- **Nested quoting:** Escaping differs between Bash and Zsh; multi-line JS in one string is fragile.
+
+**Allowed:** Trivial one-line only if it has **no** backticks, no `!`, no nested quotes, no multi-line, no `fs` usage. Example: `node -e "console.log(1+1)"`. If in doubt, **use a script file**.
+
+---
+
+## 2. How To Generate CLI Commands Correctly
+
+### Run Node scripts by path, not inline code
+
+- **Do:** `node scripts/setup-cli.mjs --target-org myorg`
+- **Do:** `node path/to/script.mjs arg1 arg2`
+- **Do not:** `node -e "require('fs').writeFileSync(...)"` or any non-trivial inline JS.
+
+### For file edits or transforms
+
+1. **Prefer IDE/agent file tools** (StrReplace, Write, etc.) — they avoid the shell.
+2. **Otherwise:** write a **temporary `.js` or `.mjs` file**, run it, then remove it. Use a **heredoc with quoted delimiter** so the shell does not interpret `$`, `` ` ``, or `!`:
+
+```bash
+cat > /tmp/_transform.js << 'SCRIPT'
+const fs = require('fs');
+const data = JSON.parse(fs.readFileSync('package.json', 'utf8'));
+data.name = 'my-app';
+fs.writeFileSync('package.json', JSON.stringify(data, null, 2) + '\n');
+SCRIPT
+node /tmp/_transform.js && rm /tmp/_transform.js
+```
+
+3. **Simple replacements:** `sed -i '' 's/old/new/g' path/to/file` (macOS: `-i ''`).
+4. **JSON:** `jq '.name = "my-app"' package.json > tmp.json && mv tmp.json package.json`.
+
+### Quoting and shell safety
+
+- Use **single quotes** around the outer shell string when the inner content has `$`, `` ` ``, or `!`.
+- For heredocs that must be literal, use **`<< 'END'`** (quoted delimiter) so the body is not expanded.
+- **Do not** generate commands that rely on Bash-only features (e.g. `[[ ]]` is fine in Zsh; avoid `source` vs `.` if you need POSIX).
+
+### Paths and working directory
+
+- **State where to run from** when it matters, e.g. "From project root" or "From `force-app/main/default/webapplications/<appName>`".
+- Prefer **explicit paths** or `cd <dir> && ...` so the command is copy-paste safe.
+- This project: setup is `node scripts/setup-cli.mjs --target-org <alias>` from **project root**. Web app commands (`npm run dev`, `npm run build`, `npm run lint`) run from the **web app directory** (e.g. `force-app/main/default/webapplications/<appName>` or `**/webapplications/<appName>`).
+
+### npm / npx
+
+- Use **exact package names** (e.g. `npx @salesforce/webapps-features-experimental list`).
+- For app-specific scripts, **cd to the web app directory first**, then run `npm run <script>` or `npm install ...`.
+- Chain steps with `&&`; one logical command per line is clearer than one giant line.
+
+### Summary checklist when generating a command
+
+- [ ] No `node -e` / `node -p` / `node --eval` with complex or multi-line code.
+- [ ] If Node logic is needed, use `node path/to/script.mjs` or a temp script with heredoc `<< 'SCRIPT'`.
+- [ ] No unescaped `!`, `` ` ``, or `$` in double-quoted strings in Zsh.
+- [ ] Working directory and required args (e.g. `--target-org`) are clear.
+- [ ] Prefer file-editing tools over shell one-liners when editing project files.
+
+---
+
+## 3. Violation Handling
+
+- If a generated command used a complex `node -e` one-liner, **revert and redo** using a script file, `sed`/`jq`, or IDE file tools.
+- If the user sees `event not found`, `unexpected token`, or garbled output, **check for**:
+  - `node -e` with special characters,
+  - Double-quoted strings containing `!` or backticks,
+  - Wrong working directory or missing args.
+
+**Cross-reference:** **webapp.md** (MUST FOLLOW #1) summarizes the no–`node -e` rule; this file is the full reference for CLI command generation and alternatives.

package/dist/.a4drules/webapp-react-code-quality.md

@@ -1,7 +1,7 @@
 ---
 description: Code quality and build validation standards
 paths:
-  - "force-app/main/default/webapplications/**/*"
+  - "**/webapplications/**/*"
 ---
 
 # Code Quality & Build Validation

package/dist/.a4drules/webapp-react-typescript.md

@@ -1,7 +1,7 @@
 ---
 description: Strict TypeScript standards for type-safe React applications
 paths:
-  - "force-app/main/default/webapplications/**/*"
+  - "**/webapplications/**/*"
 ---
 
 # TypeScript Standards

package/dist/.a4drules/webapp-react.md

@@ -1,7 +1,7 @@
 ---
 description: React-specific patterns and Salesforce data access for SFDX web apps
 paths:
-  - "force-app/main/default/webapplications/**/*"
+  - "**/webapplications/**/*"
 ---
 
 # React Web App (SFDX)

package/dist/.a4drules/webapp-skills-first.md

@@ -1,7 +1,7 @@
 ---
 description: Always search for and read relevant skills before starting any task
 paths:
-  - "force-app/main/default/webapplications/**/*"
+  - "**/webapplications/**/*"
 ---
 
 # Skills-First Protocol (MUST FOLLOW)

package/dist/.a4drules/webapp.md

@@ -1,7 +1,7 @@
 ---
 description: Core web application rules for SFDX React apps
 paths:
-  - "force-app/main/default/webapplications/**/*"
+  - "**/webapplications/**/*"
 ---
 
 # Skills-First (MUST FOLLOW)
@@ -81,7 +81,7 @@ Agents consistently miss these. **You must not leave them default.**
 
 # Shell Command Safety (MUST FOLLOW)
 
-**Never use complex `node -e` one-liners** for file edits or multi-line transforms. They break in Zsh due to `!` history expansion and backtick interpolation. Use a temporary `.js` file, `sed`/`awk`, `jq`, or IDE file-editing tools instead. See **webapp-no-node-e.md** for full details and approved alternatives.
+**Never use complex `node -e` one-liners** for file edits or multi-line transforms. They break in Zsh due to `!` history expansion and backtick interpolation. Use a temporary `.js` file, `sed`/`awk`, `jq`, or IDE file-editing tools instead. See **webapp-cli-commands.md** for full details and approved alternatives.
 
 # Development Cycle
 

package/dist/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.93.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.92.1...v1.93.0) (2026-03-11)
+
+**Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental
+
+
+
+
+
 ## [1.92.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.92.0...v1.92.1) (2026-03-11)
 
 

package/dist/force-app/main/default/webapplications/appreactsampleb2x/package.json

@@ -15,8 +15,8 @@
     "graphql:schema": "node scripts/get-graphql-schema.mjs"
   },
   "dependencies": {
-    "@salesforce/sdk-data": "^1.92.1",
-    "@salesforce/webapp-experimental": "^1.92.1",
+    "@salesforce/sdk-data": "^1.93.0",
+    "@salesforce/webapp-experimental": "^1.93.0",
     "@tailwindcss/vite": "^4.1.17",
     "@tanstack/react-form": "^1.28.4",
     "@types/leaflet": "^1.9.21",
@@ -43,7 +43,7 @@
     "@graphql-eslint/eslint-plugin": "^4.1.0",
     "@graphql-tools/utils": "^11.0.0",
     "@playwright/test": "^1.49.0",
-    "@salesforce/vite-plugin-webapp-experimental": "^1.92.1",
+    "@salesforce/vite-plugin-webapp-experimental": "^1.93.0",
     "@testing-library/jest-dom": "^6.6.3",
     "@testing-library/react": "^16.1.0",
     "@testing-library/user-event": "^14.5.2",

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.92.1",
+  "version": "1.93.0",
   "description": "Base SFDX project template",
   "private": true,
   "files": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-app-react-sample-b2x-experimental",
-  "version": "1.92.1",
+  "version": "1.93.0",
   "description": "B2C sample app template with app shell",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",

package/dist/.a4drules/webapp-no-node-e.md

@@ -1,65 +0,0 @@
----
-description: No complex node -e one-liners — use temp .js files or sed/awk instead
-paths:
-  - "force-app/main/default/webapplications/**/*"
----
-
-# A4D Enforcement: No `node -e` One-Liners
-
-This project **forbids** using `node -e` (or `node -p`, `node --eval`) one-liners for any operation—file manipulation, string replacement, reading/writing configs, or shell automation.
-
-## Why This Exists
-
-Complex `node -e '...'` one-liners **silently break in Zsh** (the default macOS shell) because of:
-
-- **`!` (history expansion):** Zsh interprets `!` inside double quotes as history expansion, causing `event not found` errors or silent corruption.
-- **Backtick interpolation:** Template literals (`` ` ``) are interpreted as command substitution by the shell before Node.js ever sees them.
-- **Nested quoting:** Multi-line JS crammed into a single shell string requires fragile quote escaping that differs between Bash and Zsh.
-
-These failures are **silent and intermittent**—the command may appear to succeed while producing corrupt output.
-
-## What To Do Instead
-
-### For multi-line file edits or transforms
-
-1. **Write a temporary `.js` script**, run it, then delete it:
-
-```bash
-cat > /tmp/_transform.js << 'SCRIPT'
-const fs = require('fs');
-const data = JSON.parse(fs.readFileSync('package.json', 'utf8'));
-data.name = 'my-app';
-fs.writeFileSync('package.json', JSON.stringify(data, null, 2) + '\n');
-SCRIPT
-node /tmp/_transform.js && rm /tmp/_transform.js
-```
-
-2. **Use `sed` or `awk`** for simple, single-pattern replacements with careful escaping:
-
-```bash
-sed -i '' 's/old-value/new-value/g' path/to/file
-```
-
-3. **Use `jq`** for JSON edits:
-
-```bash
-jq '.name = "my-app"' package.json > tmp.json && mv tmp.json package.json
-```
-
-4. **Use the IDE/agent file-editing tools** (replace_in_file, write_to_file, StrReplace, Write) whenever available—these bypass the shell entirely.
-
-### For simple, truly one-line expressions
-
-A trivial `node -e "console.log(1+1)"` with no special characters is acceptable, but **if the expression contains any of these, use a temp file instead:**
-- Template literals (backticks)
-- `!` characters
-- Nested quotes
-- Multi-line strings
-- `fs` read/write operations
-
-## Violation Handling
-
-- If any prior step used a complex `node -e` one-liner, **revert and redo** using one of the approved methods above.
-- If a shell command fails with `event not found`, `unexpected token`, or produces garbled output, check for a `node -e` violation first.
-
-**Cross-reference:** This rule is also summarized in **webapp.md** (MUST FOLLOW #1). Both apply.