power-apps-code-app-deploy
/power-apps-code-app-deploy
Package, build, verify and publish updates to a Power Apps Code App (React/TypeScript/Vite with Dataverse). Use when the user wants to ship a change to a Code App, produce an update zip, or fix a build or push error.
- Author
- hoaiphongle0505 ↗
- Repository
- claude-power-platform-toolkit ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Package, build, verify and publish updates to a Power Apps Code App (React/TypeScript/Vite with Dataverse). Use when the user wants to ship a change to a Code App, produce an update zip, or fix a build or push error.
Original author description
Package, build, verify and publish updates to a Power Apps Code App (React/TypeScript/Vite with Dataverse). Use when the user wants to ship a change to a Code App, produce an update zip, or fix a build or push error.
How it works
- Workflow
- Checks before delivering
- Pitfalls
SKILL.md preview
--- name: power-apps-code-app-deploy description: Package, build, verify and publish updates to a Power Apps Code App (React/TypeScript/Vite with Dataverse). Use when the user wants to ship a change to a Code App, produce an update zip, or fix a build or push error. --- # Power Apps Code App: build, package, push Use this for a Code App written in React + TypeScript + Vite that reads and writes Dataverse. ## Workflow 1. **Make the change in the project source.** Keep edits small and focused. 2. **Build before you hand anything over.** Run the type check and `npm run build` in your own workspace. Never give the user code you have not built. 3. **Package a cumulative update zip.** The zip must contain every file changed since the last version the user installed (not only the latest edit), at the same relative paths, so the user can extract it over the project folder and nothing is missing. Name it `app-update-<N>.zip` and increase `N` each time. 4. **Give the user the deploy steps** (they run on the user's machine): 1. Extract the zip over the project folder. 2. `npm run build` 3. `pa app push` (Power Platform CLI, signed in to the right environment) 4. Hard refresh the app (Ctrl+F5) to avoid the cached bundle. 5. **Say what changed in one or two sentences.** Do not recap every step. ## Checks before delivering - Types compile and the build finishes without errors. - New Dataverse columns use the real **logical names** (publisher prefix, lowercase). Read them from the table definition, never guess. - Choice (picklist) columns are written with the numeric value, not the label. - No secrets, tenant IDs or personal emails are added to source files. Put environment values in a config module (for example `src/lib/app-config.ts`). - If a feature needs configuration that may be missing (for example a Form URL), the code falls back gracefully instead of crashing. ## Pitfalls - Hiding an admin page in the UI is **client-side only**. Real protection needs Dataverse security roles. - A stale bundle after `pa app push` is usually the browser cache. Hard refresh first before debugging. - QR codes or links that embed a URL must be regenerated and reprinted whenever the URL format changes. Tell the user when printed labels become outdated. - Do not ask the user for screenshots of the app to verify your work. Run it, read the code, and check data through the API yourself.
Versions
The database has no other skills named power-apps-code-app-deploy.
Database snapshot: 13.11.2026 · package version 05f2c0919281 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100power-apps-code-apps
Use when building, scaffolding, debugging, or deploying Microsoft Power Apps Code Apps using React, Vue, or TypeScript in VS Code. Handles project initialization via pac CLI, Dataverse and connector data access via the @microsoft/power-apps SDK, power.config.json configuration,… - 100deploy
Use to deploy, publish, or push an Expo/React Native Power Apps mobile app to a Power Platform tenant. - 100add-dataverse
Adds Dataverse tables to a Power Apps code app with generated TypeScript models and services. Can also create new Dataverse tables. Use when connecting to Dataverse, adding tables, creating schema, or querying Dataverse data. - 90code-apps
Use for Power Apps Code Apps - the pro-code model where a standalone Vite-built React/Vue/TS single-page app uses the `@microsoft/power-apps` client library and is pushed into a Power Platform environment with no server to manage. Covers scaffolding from the official Vite… - 95power-apps-code-apps
Power Apps Code Apps development standards and best practices for TypeScript, React, and Power Platform integration Triggers on: **/*.{ts,tsx,js,jsx}, **/vite.config.*, **/package.json, **/tsconfig.json, **/power.config.json - 90migrate-to-dataverse
Read the YAML files of an existing Canvas App and replace Power FX data source calls with equivalent Dataverse table calls. USE WHEN the user wants to migrate, replace, or update data source references in pa.yaml files to point to Dataverse tables.