orchardcore-asset-manager

Builds, watches, and manages frontend assets for OrchardCore modules and themes.

8.2k|2.6k|Updated Nov 19, 2014
One-click install
npx skills add https://github.com/OrchardCMS/OrchardCore --skill orchardcore-asset-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchardcore-asset-manager
Source: https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager
Command: npx skills add https://github.com/OrchardCMS/OrchardCore --skill orchardcore-asset-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OrchardCore modules and themes contain SCSS, JS, TS, and Vue source files that must be compiled into committed wwwroot output using a three-tier package structure and multiple bundlers. This Skill removes the guesswork around build commands, Node.js version prompts, Assets.json configuration, and common build failures.

Core Features & Use Cases

  • Asset Builds and Watch Mode: Run full or scoped builds with yarn build, watch, host, clean, and dry-run commands keyed to Assets.json names and tags.
  • All Action Types Covered: Configure vite, sass, min, copy, concat, parcel, webpack, and run actions via the references/actions.md guide.
  • Code Quality and Troubleshooting: Type-check with yarn check, lint with yarn lint, and resolve issues like stale Parcel caches or missing packages.
  • Use Case: After editing a Vue component in the Media module, run a scoped build with echo "1" | yarn build -n media-app, verify the wwwroot output changed, and commit both source and generated files.

Quick Start

Ask the assistant to rebuild the media-app asset in OrchardCore and verify the generated wwwroot files are up to date.

Frequently Asked Questions about orchardcore-asset-manager

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

FAQPage Schema
How do I build frontend assets in OrchardCore?

Run echo "1" | yarn build from the repository root to build all assets, or scope it with -n using the name field from the module's Assets.json, for example echo "1" | yarn build -n media-app. Built files go to the module's wwwroot folder and must be committed.

How do I add a new asset to an OrchardCore module or theme?

Create or edit the module's Assets.json with an entry specifying an action (vite, sass, min, copy, concat, parcel, webpack, or run), a name, and a source path. Run echo "1" | yarn dry-run -n name to verify paths, then build and commit the wwwroot output.

What Node.js version does the OrchardCore asset build require?

The repository pins Node.js 24.x in .node-version. The build script detects mismatches and prompts; choose option 1 to continue anyway or option 3 to install Node 24 via fnm before building.

Why are my OrchardCore asset changes not showing in the running app?

The most common cause is forgetting to rebuild after editing source files. Compare timestamps of the source file and the wwwroot bundle; if the bundle is older, run yarn build -n asset-name and confirm the generated files changed.

How do I fix 'Cannot find package' errors during the OrchardCore build?

Run fnm exec --using 24.14.1 -- corepack yarn install to install missing workspace dependencies. Re-run this after modifying any package.json in the root, .scripts/assets-manager/, or a module's Assets folder.

How do I type-check and lint Vue and TypeScript files in OrchardCore?

Run yarn check to execute vue-tsc --noEmit across all Vue/TS sources, and yarn lint to run ESLint, optionally scoped to a directory. These commands bypass the Node.js version prompt and should pass before committing.