@salesforce/webapp-template-cli-experimental 1.62.2 → 1.63.0

package/README.md

@@ -19,14 +19,14 @@ npm run build --workspace=@salesforce/webapp-template-cli-experimental
 npm run apply-patches -- <feature-path> <app-path> <target-dir>
 
 # Examples:
-# Apply shadcn UI patches to my-app (using base-react-app as reference)
-npm run apply-patches -- packages/template/feature/feature-react-shadcn packages/template/base-app/base-react-app my-app
+# Apply a feature (e.g. chart) to my-app (using base-react-app as reference)
+npm run apply-patches -- packages/template/feature/feature-react-chart packages/template/base-app/base-react-app my-app
 
 # Skip dependency installation
-npm run apply-patches -- packages/template/feature/feature-react-shadcn packages/template/base-app/base-react-app my-app --skip-dependency-changes
+npm run apply-patches -- packages/template/feature/feature-react-chart packages/template/base-app/base-react-app my-app --skip-dependency-changes
 
 # Reset target directory to base app state before applying (preserves node_modules)
-npm run apply-patches -- packages/template/feature/feature-react-shadcn packages/template/base-app/base-react-app my-app --reset
+npm run apply-patches -- packages/template/feature/feature-react-chart packages/template/base-app/base-react-app my-app --reset
 ```
 
 ### Direct usage
@@ -141,9 +141,9 @@ The CLI tool:
 ### Example: Apply feature patches to create a new app
 
 ```bash
-$ npm run apply-patches -- packages/template/feature/feature-react-shadcn packages/template/base-app/base-react-app my-app
+$ npm run apply-patches -- packages/template/feature/feature-react-chart packages/template/base-app/base-react-app my-app
 
-Applying patches: packages/template/feature/feature-react-shadcn → my-app
+Applying patches: packages/template/feature/feature-react-chart → my-app
 ℹ Validating paths...
 ✓ Validation passed
 ℹ Creating target directory my-app...
@@ -153,13 +153,12 @@ Resolving Dependencies
 ℹ No dependencies to resolve
 
 
-Applying: packages/template/feature/feature-react-shadcn
+Applying: packages/template/feature/feature-react-chart
 ℹ Discovering files...
 ℹ Found 14 file(s)
 ℹ Validating paths...
 ✓ Paths validated
-✓ Added webapplications/feature-react-shadcn/src/components/ui/button.tsx
-✓ Added webapplications/feature-react-shadcn/src/components/ui/card.tsx
+✓ Added webapplications/feature-react-chart/src/...
 ...
 
 Installing dependencies
@@ -248,7 +247,7 @@ import type { Feature } from "../cli/src/types.js";
 const feature: Feature = {
   // This feature depends on shadcn UI feature
   // shadcn will be applied first, then this feature
-  dependencies: ["packages/template/feature/feature-react-shadcn"],
+  dependencies: ["packages/template/feature/feature-react-chart"],
   packageJson: {
     dependencies: {
       "some-package": "^1.0.0",
@@ -281,7 +280,7 @@ export default feature;
 **Notes:**
 
 - `templateDir`: All files in this directory will be discovered and applied to the target app
-- `webAppName`: Used to construct the default route path and organize files. Defaults to the feature directory name (e.g., `feature-react-shadcn` → `feature-react-shadcn`)
+- `webAppName`: Used to construct the default route path and organize files. Defaults to the feature directory name (e.g., `feature-react-chart` → `feature-react-chart`)
 - `routeFilePath`: Must be a path relative to `templateDir`. If not specified, defaults to `webapplications/<webAppName>/src/routes.tsx`
 
 ## Path Mappings
@@ -290,10 +289,10 @@ Path mappings allow features to use simplified directory structures that are aut
 
 ### Default Behavior (Enabled by Default)
 
-By default, all features automatically get the `webApp` mapping, which transforms web application files into the proper nested structure. For example, in `feature-react-shadcn`:
+By default, all features automatically get the `webApp` mapping, which transforms web application files into the proper nested structure. For example, in `feature-react-chart`:
 
 ```
-template/webApp/src/app.tsx → dist/webapplications/feature-react-shadcn/src/app.tsx
+template/webApp/src/app.tsx → dist/webapplications/feature-react-chart/src/app.tsx
 ```
 
 This simplifies feature templates by removing the repetitive nested directory structure.
@@ -301,10 +300,10 @@ This simplifies feature templates by removing the repetitive nested directory st
 **Important**: Only files under `webApp/` get the nested structure. SFDX metadata types (like `classes/`, `triggers/`, `objects/`, `lwc/`, etc.) are placed at root level:
 
 ```
-feature-react-shadcn/template/
+feature-react-chart/template/
 ├── webApp/
 │   └── src/
-│       └── app.tsx          → dist/webapplications/feature-react-shadcn/src/app.tsx
+│       └── app.tsx          → dist/webapplications/feature-react-chart/src/app.tsx
 └── classes/
     └── MyClass.cls          → dist/classes/MyClass.cls (root level)
 ```
@@ -506,7 +505,7 @@ The CLI builds a complete dependency graph and applies features in topological o
 ### Example: Building on Shared UI Features
 
 ```typescript
-// packages/template/feature/feature-react-shadcn/feature.ts
+// packages/template/feature/feature-react-chart/feature.ts
 import type { Feature } from "../../../cli/src/types.js";
 
 const feature: Feature = {
@@ -522,7 +521,7 @@ import type { Feature } from "../../../cli/src/types.js";
 
 const feature: Feature = {
   // Admin dashboard builds on top of shadcn UI
-  dependencies: ["packages/template/feature/feature-react-shadcn"],
+  dependencies: ["packages/template/feature/feature-react-chart"],
 };
 
 export default feature;
@@ -530,8 +529,8 @@ export default feature;
 
 When you apply `feature-admin-dashboard`:
 
-1. CLI resolves `feature-react-shadcn` as a dependency
-2. Applies `feature-react-shadcn` first (UI components)
+1. CLI resolves `feature-react-chart` as a dependency
+2. Applies `feature-react-chart` first
 3. Applies `feature-admin-dashboard` second (dashboard files and routes)
 4. Result: App has both shared UI and admin dashboard
 
@@ -574,7 +573,7 @@ When multiple features modify the same file:
 Example:
 
 ```
-feature-react-shadcn provides: src/appLayout.tsx
+Features can provide e.g. src/appLayout.tsx
 feature-custom-app also provides: src/appLayout.tsx
 
 When applying feature-custom-app:
@@ -635,7 +634,7 @@ Routes accumulate across all features, preserving routes from base app and all d
 
 Dependency paths can be:
 
-- **Relative to monorepo root**: `'packages/template/feature/feature-react-shadcn'`
+- **Relative to monorepo root**: `'packages/template/feature/feature-react-chart'`
 - **Absolute paths**: `'/absolute/path/to/feature'`
 
 The CLI normalizes and resolves all paths consistently.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-cli-experimental",
-  "version": "1.62.2",
+  "version": "1.63.0",
   "description": "CLI tool for applying feature patches to base apps",
   "license": "SEE LICENSE IN LICENSE.txt",
   "type": "module",