skills.rest
OpenAEC-Foundation
OpenAEC-FoundationOFFICIAL
Explore all skills by this author →
GitHub

frappe-ops-frontend-build

Migrate Frappe frontend builds from build.json to esbuild workflows.

163|53|Updated Jan 14, 2026
Search Tags:#css#esbuild#scss#frontend-build#build.json#asset-bundling
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package --skill frappe-ops-frontend-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frappe-ops-frontend-build
Source: https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-frontend-build
Command: npx skills add https://github.com/OpenAEC-Foundation/Frappe_Claude_Skill_Package --skill frappe-ops-frontend-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating and validating Frappe frontend builds from the legacy build.json system to the esbuild-based workflow, preventing misconfigurations that break asset pipelines across v14–v16.

Core Features & Use Cases

  • Supports migration from build.json (v14) to esbuild (v15+) and aligns frontend build configurations.
  • Validates SCSS/CSS compilation and asset bundling with bundle.js across environments.
  • Provides troubleshooting guidance for production builds and bench workflows to ensure reliable asset delivery.

Quick Start

Configure your project’s frontend build by migrating from build.json to esbuild and run a production bench build to verify assets.

Frequently Asked Questions about frappe-ops-frontend-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Frappe frontend builds from build.json to esbuild?▼

To migrate Frappe frontend builds from build.json to esbuild, configure the v15+ esbuild workflow to replace the legacy v14 build.json system. Validate asset bundling and run a production bench build to ensure reliable asset delivery across environments.

Why does my Frappe v15 production bench build fail with SCSS compilation errors?▼

Frappe v15 production bench build SCSS compilation errors occur when esbuild configurations are misaligned during migration from build.json. Validate the esbuild asset bundling setup and SCSS compilation configurations to prevent breaking the frontend asset pipeline.

Do I need esbuild to bundle CSS and SCSS assets in Frappe v15?▼

Yes, esbuild handles CSS and SCSS asset bundling in Frappe v15+. Configuring esbuild correctly ensures the bundle.js workflow compiles stylesheets properly across development and production environments, replacing the legacy build.json system.

What is the best way to configure asset bundling for a Frappe v15 app?▼

The best way to configure Frappe v15 asset bundling is migrating from build.json to the esbuild-based workflow. This aligns frontend build configurations and validates bundle.js outputs, ensuring safe and documented asset delivery across development and production.

Can I use legacy build.json configurations with Frappe v14 during an esbuild migration?▼

Yes, the migration supports v14 legacy build.json configurations while transitioning to esbuild for v15+. This ensures frontend builds remain intact and provides documented guidance for aligning asset pipelines safely across v14–v16 environments.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
163

frappe-ops-bench

Automate bench CLI workflows for Frappe deployments.

Official
Advanced
corey-alixcorey-alix

css-imports-typescript-esbuild

Compare tsc and esbuild CSS import handling in TypeScript projects.

Official
Intermediate
Impertio-StudioImpertio-Studio
163

frappe-ops-frontend-build

Align Frappe asset bundling configuration to v15+ esbuild conventions.

Official
Advanced
BerryKuipersBerryKuipers
7

validate-build

Run production build validation across Vite, TypeScript, Webpack, esbuild, and Rollup.

Community
Intermediate