create-ec-app 0.0.2 → 0.0.4

package/dist/index.js

@@ -6,8 +6,8 @@ import { createPortalApp } from "./creators/portal.js";
 import { createPowerPagesApp } from "./creators/powerpages.js";
 import { createMobileApp } from "./creators/mobile.js";
 const main = async () => {
-    console.log(chalk.bold.hex("#F5AB00")("\n🚀 Welcome to EC App Creator!\n"));
-    console.log(chalk.gray("Create different types of applications for your EC ecosystem.\n"));
+    console.log(chalk.bold.hex("#F5AB00")("\nEC App Creator\n"));
+    console.log(chalk.gray("Create applications for your EC ecosystem.\n"));
     // Prompt for project name if not provided
     let projectName = process.argv[2];
     if (!projectName) {
@@ -26,24 +26,24 @@ const main = async () => {
     // Prompt for application type
     const appTypes = [
         {
-            name: "📱 Webresource App",
+            name: "Webresource App",
             value: "webresource",
-            description: "React app for Dynamics 365 webresources with Vite, Kendo UI, and Tailwind"
+            description: "React app for Dynamics 365 webresources with Vite, optional Kendo UI, and Tailwind"
         },
         {
-            name: "🌐 Portal App",
+            name: "Portal App",
             value: "portal",
             description: "Next.js app for customer portals with authentication and Dynamics integration"
         },
         {
-            name: "⚡ Power Pages App",
+            name: "Power Pages App",
             value: "powerpages",
-            description: "React SPA for Power Pages with specialized authentication and data services"
+            description: "React SPA for Power Pages with authentication context and data services"
         },
         {
-            name: "📲 Mobile App",
+            name: "Mobile App",
             value: "mobile",
-            description: "React Native Expo app with NativeWind, TypeScript, and MSAL authentication"
+            description: "React Native Expo app with TypeScript and NativeWind"
         }
     ];
     const { appType } = await inquirer.prompt([
@@ -54,12 +54,12 @@ const main = async () => {
             choices: appTypes.map(type => ({
                 name: `${type.name}\n  ${chalk.gray(type.description)}`,
                 value: type.value,
-                short: type.name.replace(/[📱🌐⚡📲]/g, '').trim()
+                short: type.name
             })),
             pageSize: 10
         },
     ]);
-    console.log(`\n${chalk.green("✨ Creating")} ${chalk.bold(appType)} app: ${chalk.cyan(projectName)}\n`);
+    console.log(`\n${chalk.green("Creating")} ${chalk.bold(appType)} app: ${chalk.cyan(projectName)}\n`);
     // Route to the appropriate creator
     switch (appType) {
         case "webresource":
@@ -79,17 +79,17 @@ const main = async () => {
             process.exit(1);
     }
     // Final success message
-    console.log(chalk.green.bold("\n🎉 Project created successfully!"));
+    console.log(chalk.green.bold("\nProject created successfully."));
     console.log(`\n${chalk.cyan("Next steps:")}`);
-    console.log(`  ${chalk.gray("›")} cd ${projectName}`);
+    console.log(`  - cd ${projectName}`);
     if (appType === "webresource" || appType === "powerpages") {
-        console.log(`  ${chalk.gray("›")} ${chalk.yellow("npx kendo-ui-license activate")} ${chalk.gray("(IMPORTANT: Activate your Kendo license)")}`);
+        console.log(`  - If you selected Kendo UI: ${chalk.yellow("npx kendo-ui-license activate")}`);
     }
-    console.log(`  ${chalk.gray("›")} npm run dev`);
-    console.log(`  ${chalk.gray("›")} npm run build\n`);
+    console.log(`  - npm run dev`);
+    console.log(`  - npm run build\n`);
 };
 main().catch((error) => {
-    console.error(chalk.red("❌ An error occurred:"), error);
+    console.error(chalk.red("An error occurred:"), error);
     process.exit(1);
 });
 //# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAEA,OAAO,KAAK,MAAM,OAAO,CAAC;AAC1B,OAAO,QAAQ,MAAM,UAAU,CAAC;AAChC,OAAO,EAAE,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AACvD,OAAO,EAAE,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAQvD,MAAM,IAAI,GAAG,KAAK,IAAmB,EAAE;IACtC,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,mCAAmC,CAAC,CAAC,CAAC;IAC5E,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,iEAAiE,CAAC,CAAC,CAAC;IAE3F,0CAA0C;IAC1C,IAAI,WAAW,GAAW,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC1C,IAAI,CAAC,WAAW,EAAE,CAAC;QAClB,MAAM,EAAE,cAAc,EAAE,GAAG,MAAM,QAAQ,CAAC,MAAM,CAA6B;YAC5E;gBACC,IAAI,EAAE,OAAO;gBACb,IAAI,EAAE,gBAAgB;gBACtB,OAAO,EAAE,mCAAmC;gBAC5C,QAAQ,EAAE,CAAC,KAAa,EAAE,EAAE,CAC3B,KAAK,KAAK,GAAG;oBACb,kBAAkB,CAAC,IAAI,CAAC,KAAK,CAAC;oBAC9B,oIAAoI;aACrI;SACD,CAAC,CAAC;QACH,WAAW,GAAG,cAAc,CAAC;IAC9B,CAAC;IAED,8BAA8B;IAC9B,MAAM,QAAQ,GAAoB;QACjC;YACC,IAAI,EAAE,oBAAoB;YAC1B,KAAK,EAAE,aAAa;YACpB,WAAW,EAAE,2EAA2E;SACxF;QACD;YACC,IAAI,EAAE,eAAe;YACrB,KAAK,EAAE,QAAQ;YACf,WAAW,EAAE,+EAA+E;SAC5F;QACD;YACC,IAAI,EAAE,mBAAmB;YACzB,KAAK,EAAE,YAAY;YACnB,WAAW,EAAE,6EAA6E;SAC1F;QACD;YACC,IAAI,EAAE,eAAe;YACrB,KAAK,EAAE,QAAQ;YACf,WAAW,EAAE,4EAA4E;SACzF;KACD,CAAC;IAEF,MAAM,EAAE,OAAO,EAAE,GAAG,MAAM,QAAQ,CAAC,MAAM,CAAsB;QAC9D;YACC,IAAI,EAAE,MAAM;YACZ,IAAI,EAAE,SAAS;YACf,OAAO,EAAE,oDAAoD;YAC7D,OAAO,EAAE,QAAQ,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;gBAC9B,IAAI,EAAE,GAAG,IAAI,CAAC,IAAI,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE;gBACvD,KAAK,EAAE,IAAI,CAAC,KAAK;gBACjB,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;aACjD,CAAC,CAAC;YACH,QAAQ,EAAE,EAAE;SACZ;KACD,CAAC,CAAC;IAEH,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,KAAK,CAAC,YAAY,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,SAAS,KAAK,CAAC,IAAI,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAEvG,mCAAmC;IACnC,QAAQ,OAAO,EAAE,CAAC;QACjB,KAAK,aAAa;YACjB,MAAM,oBAAoB,CAAC,WAAW,CAAC,CAAC;YACxC,MAAM;QACP,KAAK,QAAQ;YACZ,MAAM,eAAe,CAAC,WAAW,CAAC,CAAC;YACnC,MAAM;QACP,KAAK,YAAY;YAChB,MAAM,mBAAmB,CAAC,WAAW,CAAC,CAAC;YACvC,MAAM;QACP,KAAK,QAAQ;YACZ,MAAM,eAAe,CAAC,WAAW,CAAC,CAAC;YACnC,MAAM;QACP;YACC,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC,qBAAqB,OAAO,EAAE,CAAC,CAAC,CAAC;YACzD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,wBAAwB;IACxB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,oCAAoC,CAAC,CAAC,CAAC;IACpE,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,aAAa,CAAC,EAAE,CAAC,CAAC;IAC9C,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,OAAO,WAAW,EAAE,CAAC,CAAC;IACtD,IAAI,OAAO,KAAK,aAAa,IAAI,OAAO,KAAK,YAAY,EAAE,CAAC;QAC3D,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,+BAA+B,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,0CAA0C,CAAC,EAAE,CAAC,CAAC;IAChJ,CAAC;IACD,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,cAAc,CAAC,CAAC;IAChD,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,kBAAkB,CAAC,CAAC;AACrD,CAAC,CAAC;AAEF,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACtB,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC,sBAAsB,CAAC,EAAE,KAAK,CAAC,CAAC;IACxD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AACjB,CAAC,CAAC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAEA,OAAO,KAAK,MAAM,OAAO,CAAC;AAC1B,OAAO,QAAQ,MAAM,UAAU,CAAC;AAChC,OAAO,EAAE,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AACvD,OAAO,EAAE,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAQvD,MAAM,IAAI,GAAG,KAAK,IAAmB,EAAE;IACtC,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,oBAAoB,CAAC,CAAC,CAAC;IAC7D,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,8CAA8C,CAAC,CAAC,CAAC;IAExE,0CAA0C;IAC1C,IAAI,WAAW,GAAW,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC1C,IAAI,CAAC,WAAW,EAAE,CAAC;QAClB,MAAM,EAAE,cAAc,EAAE,GAAG,MAAM,QAAQ,CAAC,MAAM,CAA6B;YAC5E;gBACC,IAAI,EAAE,OAAO;gBACb,IAAI,EAAE,gBAAgB;gBACtB,OAAO,EAAE,mCAAmC;gBAC5C,QAAQ,EAAE,CAAC,KAAa,EAAE,EAAE,CAC3B,KAAK,KAAK,GAAG;oBACb,kBAAkB,CAAC,IAAI,CAAC,KAAK,CAAC;oBAC9B,oIAAoI;aACrI;SACD,CAAC,CAAC;QACH,WAAW,GAAG,cAAc,CAAC;IAC9B,CAAC;IAED,8BAA8B;IAC9B,MAAM,QAAQ,GAAoB;QACjC;YACC,IAAI,EAAE,iBAAiB;YACvB,KAAK,EAAE,aAAa;YACpB,WAAW,EAAE,oFAAoF;SACjG;QACD;YACC,IAAI,EAAE,YAAY;YAClB,KAAK,EAAE,QAAQ;YACf,WAAW,EAAE,+EAA+E;SAC5F;QACD;YACC,IAAI,EAAE,iBAAiB;YACvB,KAAK,EAAE,YAAY;YACnB,WAAW,EAAE,yEAAyE;SACtF;QACD;YACC,IAAI,EAAE,YAAY;YAClB,KAAK,EAAE,QAAQ;YACf,WAAW,EAAE,sDAAsD;SACnE;KACD,CAAC;IAEF,MAAM,EAAE,OAAO,EAAE,GAAG,MAAM,QAAQ,CAAC,MAAM,CAAsB;QAC9D;YACC,IAAI,EAAE,MAAM;YACZ,IAAI,EAAE,SAAS;YACf,OAAO,EAAE,oDAAoD;YAC7D,OAAO,EAAE,QAAQ,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;gBAC9B,IAAI,EAAE,GAAG,IAAI,CAAC,IAAI,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE;gBACvD,KAAK,EAAE,IAAI,CAAC,KAAK;gBACjB,KAAK,EAAE,IAAI,CAAC,IAAI;aAChB,CAAC,CAAC;YACH,QAAQ,EAAE,EAAE;SACZ;KACD,CAAC,CAAC;IAEH,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,KAAK,CAAC,UAAU,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,SAAS,KAAK,CAAC,IAAI,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAErG,mCAAmC;IACnC,QAAQ,OAAO,EAAE,CAAC;QACjB,KAAK,aAAa;YACjB,MAAM,oBAAoB,CAAC,WAAW,CAAC,CAAC;YACxC,MAAM;QACP,KAAK,QAAQ;YACZ,MAAM,eAAe,CAAC,WAAW,CAAC,CAAC;YACnC,MAAM;QACP,KAAK,YAAY;YAChB,MAAM,mBAAmB,CAAC,WAAW,CAAC,CAAC;YACvC,MAAM;QACP,KAAK,QAAQ;YACZ,MAAM,eAAe,CAAC,WAAW,CAAC,CAAC;YACnC,MAAM;QACP;YACC,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC,qBAAqB,OAAO,EAAE,CAAC,CAAC,CAAC;YACzD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,wBAAwB;IACxB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,iCAAiC,CAAC,CAAC,CAAC;IACjE,OAAO,CAAC,GAAG,CAAC,KAAK,KAAK,CAAC,IAAI,CAAC,aAAa,CAAC,EAAE,CAAC,CAAC;IAC9C,OAAO,CAAC,GAAG,CAAC,UAAU,WAAW,EAAE,CAAC,CAAC;IACrC,IAAI,OAAO,KAAK,aAAa,IAAI,OAAO,KAAK,YAAY,EAAE,CAAC;QAC3D,OAAO,CAAC,GAAG,CAAC,iCAAiC,KAAK,CAAC,MAAM,CAAC,+BAA+B,CAAC,EAAE,CAAC,CAAC;IAC/F,CAAC;IACD,OAAO,CAAC,GAAG,CAAC,iBAAiB,CAAC,CAAC;IAC/B,OAAO,CAAC,GAAG,CAAC,qBAAqB,CAAC,CAAC;AACpC,CAAC,CAAC;AAEF,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACtB,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,GAAG,CAAC,oBAAoB,CAAC,EAAE,KAAK,CAAC,CAAC;IACtD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AACjB,CAAC,CAAC,CAAC"}

package/dist/readmes/mobile.md

@@ -0,0 +1,42 @@
+# EC Mobile App
+
+Expo + React Native + TypeScript template with Tailwind (NativeWind-style utilities), Expo Router, and a small set of UI utilities. Generated by `create-ec-app` for rapid mobile development.
+
+## Features
+
+- Expo Router with typed layouts
+- Tailwind utilities for React Native
+- Theming helpers for React Navigation (`lib/theme.ts`)
+- Utility helpers (`lib/utils.ts` with `cn`)
+- Portal support via `@rn-primitives/portal` (included in root layout)
+
+## Prerequisites
+
+- Node.js 18+
+- Xcode (macOS) and/or Android Studio SDKs for local simulators
+- Expo CLI (installed automatically via `npx`)
+
+## Getting Started
+
+- Install dependencies: `npm install`
+- Start development: `npx expo start`
+  - Press `i` for iOS simulator, `a` for Android, or scan the QR code with Expo Go
+
+## Key Files
+
+- `app/_layout.tsx`: Root layout with theme provider, Expo Router stack, and `PortalHost`.
+- `lib/theme.ts`: Light/dark palettes mapped to React Navigation theme.
+- `lib/utils.ts`: `cn` helper for conditional class names.
+- `global.css`: Tailwind directives and custom styles (imported by the root layout).
+
+## Styling
+
+- The template uses Tailwind utilities for React Native components. Adjust Tailwind config as needed for your design system.
+
+## Building
+
+- Use the Expo tooling for builds and previews:
+  - `npx expo prebuild` to generate native projects (if needed)
+  - `npx expo run:ios` / `npx expo run:android` to build and run
+  - See the Expo docs for EAS Build for cloud builds
+

package/dist/readmes/portal.md

@@ -0,0 +1,161 @@
+# EC Portal App
+
+Next.js (App Router) + TypeScript template for customer portals integrated with Dynamics 365/Dataverse. Generated by `create-ec-app`, it includes Tailwind CSS, TanStack Query, Azure AD authentication via NextAuth, and a choice of UI library (Kendo UI or Shadcn/ui).
+
+## Features
+
+- Next.js App Router with TypeScript
+- Tailwind CSS; Kendo preset applied when using Kendo UI
+- UI choice: Kendo UI (with theme import) or Shadcn/ui
+- TanStack Query provider (`src/app/providers.tsx`)
+- Azure AD auth via NextAuth (`auth.ts`, `src/app/api/auth/[...nextauth]/route.ts`)
+- Example Dynamics API route (`src/app/api/dynamics/accounts/route.ts`)
+- React Query hook (`src/hooks/useDynamicsAccounts.ts`)
+- `next.config.ts` set to `output: 'standalone'` (Azure-friendly)
+- Example GitHub Actions workflow (`github.example.deploy.yml`)
+- Example Azure DevOps pipeline (`azure-pipelines.example.yml`)
+
+## Prerequisites
+
+- Node.js 18+ and npm 9+
+- Azure AD app registration (client id/secret, tenant)
+- Dynamics 365/Dataverse environment and base URL
+
+## Getting Started
+
+1. Install dependencies: `npm install`
+
+2. Configure environment in `.env.local`:
+
+```
+NEXTAUTH_URL=http://localhost:3000
+AZURE_AD_CLIENT_ID=your-azure-ad-client-id
+AZURE_AD_CLIENT_SECRET=your-azure-ad-client-secret
+AZURE_AD_TENANT_ID=your-azure-ad-tenant-id
+DYNAMICS_BASE_URL=https://your-org.crm.dynamics.com
+DYNAMICS_API_VERSION=v9.2
+```
+
+3. Development: `npm run dev`
+
+4. Production build: `npm run build` then `npm start`
+
+If you selected Kendo UI, activate your license after install:
+
+```
+npx kendo-ui-license activate
+```
+
+## Dynamics Data Access
+
+- Library: `src/lib/dynamics.ts` exposes `getDynamicsData(entity, options)`
+- API route: `src/app/api/dynamics/accounts/route.ts` fetches Accounts via the above
+- Hook: `src/hooks/useDynamicsAccounts.ts` wraps the API with TanStack Query
+
+Example component:
+
+```tsx
+"use client";
+import { useDynamicsAccounts } from "@/hooks/useDynamicsAccounts";
+
+export default function AccountsList() {
+	const { data, isLoading, error } = useDynamicsAccounts();
+	if (isLoading) return <div>Loading…</div>;
+	if (error) return <div>Failed to load</div>;
+	return (
+		<ul>
+			{data?.map((a) => (
+				<li key={a.accountid}>{a.name}</li>
+			))}
+		</ul>
+	);
+}
+```
+
+## UI Libraries
+
+- Kendo UI: Theme CSS is imported in `src/app/layout.tsx` and components can be used from `@progress/kendo-react-*` packages.
+- Shadcn/ui: Components are installed and available via the `@/components` alias.
+
+## Deployment
+
+- The project is configured for standalone output (good for Azure App Service and containers).
+- An example GitHub Actions workflow is provided in `example.deploy.yml`. Configure secrets and adapt steps to your environment.
+
+### Azure App Service (Web App)
+
+Step 1 — Create a Web App and connect CI
+
+- Create a new App Service in Azure and connect deployment to your repository (GitHub) or set up an Azure DevOps pipeline.
+
+Step 2 — Environment variables
+
+It is important to set configuration early to avoid restarts due to missing settings. Ensure you set the following app settings. Note the `SCM_DO_BUILD_DURING_DEPLOYMENT` flag controls whether App Service attempts a build during deployment.
+
+Example app settings payload:
+
+```
+[
+  {
+    "name": "AUTH_MICROSOFT_ENTRA_ID_ID",
+    "value": "",
+    "slotSetting": false
+  },
+  {
+    "name": "AUTH_MICROSOFT_ENTRA_ID_ISSUER",
+    "value": "<https://login.microsoftonline.com/TENANT_ID/v2.0>",
+    "slotSetting": false
+  },
+  {
+    "name": "AUTH_MICROSOFT_ENTRA_ID_SECRET",
+    "value": "CLIENT_SECRET",
+    "slotSetting": false
+  },
+  {
+    "name": "AUTH_MICROSOFT_ENTRA_ID_TENANT_ID",
+    "value": "TENANT_ID",
+    "slotSetting": false
+  },
+  {
+    "name": "AUTH_SECRET",
+    "value": "AUTH_SECRET",
+    "slotSetting": false
+  },
+  {
+    "name": "AUTH_URL",
+    "value": "https://WEBSITE_URL/",
+    "slotSetting": false
+  },
+  {
+    "name": "DYNAMICS_API_URL",
+    "value": "https://DYNAMICS_URL/",
+    "slotSetting": false
+  },
+  {
+    "name": "NEXT_PUBLIC_BASE_URL",
+    "value": "https://BASE_URL",
+    "slotSetting": false
+  },
+  {
+    "name": "SCM_DO_BUILD_DURING_DEPLOYMENT",
+    "value": "false",
+    "slotSetting": false
+  }
+]
+```
+
+Notes:
+
+- If your CI pipeline builds the app and you deploy the standalone output, set `SCM_DO_BUILD_DURING_DEPLOYMENT` to `false` to prevent an extra App Service build.
+- If you push source and want App Service (Kudu/Oryx) to build, set `SCM_DO_BUILD_DURING_DEPLOYMENT` to `true`.
+- This template’s `auth.ts` uses `AZURE_AD_CLIENT_ID|SECRET|TENANT_ID`. If you prefer Auth.js environment variable names (`AUTH_MICROSOFT_ENTRA_ID_*`), update `auth.ts` accordingly or map the variables in your deployment.
+
+Step 3 — Startup command
+
+- In App Service > Settings > Configuration, set Startup command:
+
+```
+node server.js
+```
+
+- This ensures the standalone Next.js server is launched on startup. Without it, you may see “next not found” in Log Stream and an Application Error on launch.

package/dist/readmes/powerpages.md

@@ -0,0 +1,108 @@
+# EC Power Pages Single Page Application (SPA)
+
+This is a Power Pages Single Page Application (SPA) built with React, Vite, and TypeScript, generated by `create-ec-app`. It follows Microsoft’s official Power Pages code site model, providing a modern, scalable, and maintainable frontend architecture tailored specifically for Power Pages environments. The app includes integrated authentication, data fetching, and UI options designed to work seamlessly within the Power Pages runtime.
+
+## Features
+
+- **React + Vite + TypeScript**: Modern frontend stack for fast development and optimized builds.
+- **Tailwind CSS**: Utility-first CSS framework with an optional Kendo UI preset for styling consistency.
+- **UI Library Choice**: Select between Kendo UI (including theme selection) or Shadcn/ui components.
+- **TanStack Query**: Preconfigured React Query provider for efficient data fetching and caching.
+- **Power Pages AuthContext**: Integrated authentication context that detects the Power Pages user (`Microsoft.Dynamics365.Portal.User`) and retrieves tokens via `window.shell.getTokenDeferred()`.
+- **Local Development Support**: Includes a mock token file and configuration to simulate authentication during local development.
+- **Optimized Vite Build Output**: Builds optimized assets tailored for upload to Power Pages code sites.
+
+## Auth and API Access
+
+This SPA integrates with Power Pages authentication and API access mechanisms. The `AuthContext` handles user detection and token retrieval using the Power Pages runtime API. Tokens are obtained asynchronously through `window.shell.getTokenDeferred()`, enabling authenticated API calls to Power Pages endpoints.
+
+### Example: API URL and Auth Headers
+
+Here is an example of utility functions to build API URLs and set authentication headers for requests within the Power Pages SPA:
+
+```ts
+// src/utils/api.ts
+
+export function getApiUrl(entity: string, query = ''): string {
+  // Base path for Power Pages API (adjust if your site uses a different base)
+  const baseUrl = '/_api';
+  return `${baseUrl}/${entity}${query ? `?${query}` : ''}`;
+}
+
+export function getAuthHeaders(token: string) {
+  return {
+    Authorization: `Bearer ${token}`,
+    'Content-Type': 'application/json',
+    Accept: 'application/json',
+  };
+}
+```
+
+### Azure CLI Token Generation for Local Development
+
+For local development and debugging outside the Power Pages runtime, you can generate an Azure AD token using the Azure CLI. This token can be used to simulate authenticated requests against your Power Pages environment:
+
+```bash
+az account get-access-token --resource=https://<your-powerpages-environment>.crm.dynamics.com
+```
+
+Replace `<your-powerpages-environment>` with your actual environment URL. Use the obtained token in your local mock token file or directly in API request headers.
+
+## Example Service Using TanStack Query
+
+Here is an example of a service module `src/services/contacts.ts` that demonstrates fetching contacts data from the Power Pages API using TanStack Query:
+
+```ts
+// src/services/contacts.ts
+import { useQuery } from '@tanstack/react-query';
+import { getApiUrl, getAuthHeaders } from '@/utils/api';
+import { useAuth } from '@/context/AuthContext';
+
+export interface Contact {
+  contactid: string;
+  firstname: string;
+  lastname: string;
+  emailaddress1?: string;
+}
+
+async function fetchContacts(token: string): Promise<Contact[]> {
+  const response = await fetch(getApiUrl('contacts'), {
+    headers: getAuthHeaders(token),
+  });
+  if (!response.ok) {
+    throw new Error('Failed to fetch contacts');
+  }
+  const data = await response.json();
+  return data.value;
+}
+
+export function useContacts() {
+  const { token } = useAuth();
+
+  return useQuery(['contacts'], () => fetchContacts(token!), {
+    enabled: !!token,
+  });
+}
+```
+
+This pattern leverages the `AuthContext` to access the current token and uses TanStack Query to manage caching and background updates.
+
+## Deployment
+
+To deploy your Power Pages SPA:
+
+- Build the project using `npm run build` or `npm run build:dev` for development builds.
+- Upload the contents of the `dist` folder to your Power Pages site’s **code site**. This is a dedicated location for hosting SPA assets as static content.
+- Reference your built JavaScript and CSS files in your Power Pages pages as needed.
+
+For detailed guidance on Power Pages code sites and deployment, see the [Microsoft Power Pages documentation on code sites](https://learn.microsoft.com/en-us/power-pages/developer/code-sites).
+
+Power Pages code sites support continuous deployment workflows via the Power Platform CLI, enabling streamlined updates and integration with source control.
+
+## Configuration
+
+The `powerpages.config.json` file defines your site configuration, including output paths and landing page settings. Adjust this file to match your project and deployment conventions.
+
+---
+
+This SPA template provides a robust foundation for building Power Pages applications with modern web development tools and best practices, ensuring smooth integration with the Power Pages platform and scalable, maintainable code.

package/dist/readmes/webresource.md

@@ -0,0 +1,260 @@
+# EC Webresource App
+
+React + TypeScript template for Dynamics 365/Dataverse web resources. Generated by `create-ec-app`, it provides a lean setup with Vite, Tailwind CSS, and a choice of UI library (Kendo UI or Shadcn/ui), pre-configured for running inside Dynamics 365 and for local development.
+
+## Features
+
+- React + TypeScript with Vite (Client side only)
+- Tailwind CSS configured out of the box
+- UI library choice: Kendo UI (with theme selection) or Shadcn/ui
+- TanStack Query provider pre-wired (`QueryClientProvider` in `src/main.tsx`)
+- XRM-aware runtime: adds `ClientGlobalContext.js.aspx` and detects `window.Xrm`
+- Local development via `token.json` (excluded from bundling) and helper functions
+- Vite build tuned for web resources: single JS bundle, `main.css`, deterministic names
+- Zustand and `@types/xrm` included for state and typings
+
+## Prerequisites
+
+- Node.js 18+ and npm 9+
+- Dynamics 365/Dataverse environment for deployment
+- Kendo UI license (only if you picked Kendo UI)
+
+## Getting Started
+
+- Install dependencies (if needed): `npm install`
+- For Kendo UI projects, activate your license: `npx kendo-ui-license activate` (you need to copy over your kendo-license.txt to the root to activate or stick with non-premium components)
+- Start dev server: `npm run dev`
+- Production build: `npm run build`
+- Development build (readable, no minify): `npm run build:dev`
+
+## Key Files
+
+- `src/main.tsx`: Sets up React, Tailwind, and TanStack Query. If Kendo UI was selected, imports the chosen theme CSS (`<theme>/dist/all.css`).
+- `src/services/authService.ts`: Utilities to build API URLs and headers based on environment (inside Dynamics vs. local dev).
+- `token.json`: Local development token store. Build is configured to treat this as external and not bundle it.
+- `index.html`: Injects `ClientGlobalContext.js.aspx` for Dynamics runtime.
+- `vite.config.ts`: Uses base `./`, disables code splitting, emits `main.css`, and places assets at the top of `dist`.
+
+## Auth and API Access
+
+The app auto-detects whether it runs inside Dynamics 365 (uses `window.Xrm` and does not add an Authorization header) or locally (reads a bearer token from `token.json`).
+
+```ts
+// src/services/authService.ts
+export const getApiUrl = (): string => {
+	if (window.parent && window.parent.Xrm) {
+		const clientUrl = window.Xrm.Utility.getGlobalContext().getClientUrl();
+		return `${clientUrl}/api/data/v9.2`;
+	}
+	return "https://DOMAIN.REGION.dynamics.com/api/data/v9.2";
+};
+
+export const getAuthHeaders = async (): Promise<HeadersInit> => {
+	if (window.parent && window.parent.Xrm) {
+		return {
+			"Content-Type": "application/json",
+			"OData-MaxVersion": "4.0",
+			"OData-Version": "4.0",
+			Prefer: 'odata.include-annotations="*"',
+		};
+	}
+	const { default: token } = await import("../../token.json");
+	return {
+		Authorization: `Bearer ${token.accessToken}`,
+		"Content-Type": "application/json",
+		"OData-MaxVersion": "4.0",
+		"OData-Version": "4.0",
+		Prefer: 'odata.include-annotations="*"',
+	};
+};
+```
+
+Example usage:
+
+```ts
+import { getApiUrl, getAuthHeaders } from "@/services/authService";
+
+const res = await fetch(`${getApiUrl()}/accounts?$top=10`, {
+	headers: await getAuthHeaders(),
+});
+const data = await res.json();
+```
+
+## Azure CLI: Generate a Dataverse Token (Local Dev)
+
+Use Azure CLI to obtain a bearer token for your Dataverse environment and paste it into `token.json` for local development.
+
+Prerequisites:
+
+- Azure CLI installed and you have access to the target tenant and environment.
+
+Steps:
+
+1. Sign in to Azure (optionally targeting a specific tenant):
+
+```
+az login --tenant <tenant-id>
+```
+
+2. Request an access token for your Dataverse environment URL (replace `<org>` and domain as applicable):
+
+```
+az account get-access-token \
+  --tenant <tenant-id> \
+  --resource https://<org>.crm.dynamics.com \
+```
+
+This prints the raw token to stdout. Copy it.
+
+3. Paste the token value into `token.json` under `accessToken`:
+
+```
+{
+  "accessToken": "<paste-token-here>",
+  "expiresIn": "",
+  "expires_on": 0,
+  "subscription": "",
+  "tenant": "",
+  "tokenType": "Bearer"
+}
+```
+
+Notes:
+
+- Tokens expire; regenerate as needed. (Max expiry is 1 hour)
+- If your CLI requires scopes, use `--scope https://<org>.crm.dynamics.com/.default` instead of `--resource`.
+
+One‑liner (writes full JSON to `token.json`):
+
+```
+az account get-access-token --resource=https://<org>.crm.dynamics.com > token.json
+```
+
+Replace the URL with your environment’s Dataverse URL (e.g., `https://<org>.crm.dynamics.com`, `https://<org>.crm4.dynamics.com`, etc.). This overwrites `token.json` at the project root with the full output from Azure CLI, which includes `accessToken` used by the local dev flow.
+
+## Accounts Data Service (TanStack Query)
+
+The following example shows a minimal data service and hooks to fetch and update Accounts using the Dataverse Web API and TanStack Query.
+
+Create `src/services/accounts.ts`:
+
+```ts
+import { getApiUrl, getAuthHeaders } from "@/services/authService";
+import { useMutation, useQuery, useQueryClient } from "@tanstack/react-query";
+
+export interface Account {
+	accountid: string;
+	name?: string | null;
+	description?: string | null;
+}
+
+export const listAccounts = async (): Promise<Account[]> => {
+	const res = await fetch(
+		`${getApiUrl()}/accounts?$select=accountid,name,description&$top=50`,
+		{ headers: await getAuthHeaders() }
+	);
+	if (!res.ok) throw new Error(`Failed to fetch accounts: ${res.status}`);
+	const json = await res.json();
+	return json.value as Account[];
+};
+
+export const patchAccount = async (
+	id: string,
+	data: Partial<Account>
+): Promise<void> => {
+	const headers = await getAuthHeaders();
+	const res = await fetch(`${getApiUrl()}/accounts(${id})`, {
+		method: "PATCH",
+		headers: {
+			...headers,
+		},
+		body: JSON.stringify(data),
+	});
+	if (!res.ok) throw new Error(`Failed to update account: ${res.status}`);
+};
+
+export const useAccounts = () =>
+	useQuery({ queryKey: ["accounts"], queryFn: listAccounts });
+
+export const useUpdateAccount = () => {
+	const qc = useQueryClient();
+	return useMutation({
+		mutationFn: ({ id, data }: { id: string; data: Partial<Account> }) =>
+			patchAccount(id, data),
+		onSuccess: () => {
+			qc.invalidateQueries({ queryKey: ["accounts"] });
+		},
+	});
+};
+```
+
+Usage in a component (e.g. `src/AccountsList.tsx`):
+
+```tsx
+import { useAccounts, useUpdateAccount } from "@/services/accounts";
+
+export function AccountsList() {
+	const { data, isLoading, error } = useAccounts();
+	const updateAccount = useUpdateAccount();
+
+	if (isLoading) return <div>Loading…</div>;
+	if (error) return <div>Failed to load accounts</div>;
+
+	return (
+		<ul className="space-y-2">
+			{data?.map((a) => (
+				<li key={a.accountid} className="flex items-center gap-2">
+					<span className="flex-1">{a.name ?? "(no name)"}</span>
+					<button
+						className="px-2 py-1 border rounded"
+						onClick={() =>
+							updateAccount.mutate({
+								id: a.accountid,
+								data: { name: `${a.name ?? ""}*` },
+							})
+						}
+					>
+						Rename
+					</button>
+				</li>
+			))}
+		</ul>
+	);
+}
+```
+
+## UI Libraries
+
+- Kendo UI: Theme CSS is imported in `src/main.tsx`. Example:
+  ```tsx
+  import { Button } from "@progress/kendo-react-buttons";
+  <Button>Click me</Button>;
+  ```
+- Shadcn/ui: Components are installed and available under the `@/components` alias. Example:
+  ```tsx
+  import { Button } from "@/components/ui/button";
+  <Button>Click me</Button>;
+  ```
+
+## Build Output
+
+- Output directory: `dist`
+- Single JavaScript bundle with deterministic name
+- Single CSS file: `main.css`
+- `base: "./"` to support deployment as a web resource
+
+## Deployment
+
+- Upload files from `dist` to Dynamics 365/Dataverse as web resources.
+- Use `index.html` as the HTML web resource; upload the JS bundle and `main.css` as script/style web resources referenced by it.
+- Consider automating uploads with your preferred tooling (DevOps pipelines, XrmToolBox, etc.).
+- One quick and easy way to handle deployment is with Webresource Manager.
+  - Open up webresource manager, and navigate to your specific solution
+  - Create a new root (example GlobalAccounts* or CustomDev*)
+  - Add a new folder for your webresources
+  - Upload your index.html, index.js and main.css to your folder.
+  - This will now allow you to use auto publisher to bind to your deployed resources.
+
+## Notes
+
+- If you change the build, ensure code splitting stays disabled and asset names remain predictable to simplify web resource updates.