uniapp-subpackage-uni-modules

Diagnose uni_modules inclusion in the main package for uni-app subpackage scenarios.

5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/uni-toolkit/skills --skill uniapp-subpackage-uni-modules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uniapp-subpackage-uni-modules
Source: https://github.com/uni-toolkit/skills/tree/main/skills/uniapp-subpackage-uni-modules
Command: npx skills add https://github.com/uni-toolkit/skills --skill uniapp-subpackage-uni-modules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies why uni_modules in uni-app分包 scenarios are mistakenly included in the main package, helping developers optimize their projects.

Core Features & Use Cases

  • Diagnosis of uni_modules Misplacement: Analyze the placement of uni_modules in the project structure.
  • Manifest.json and Pages.json Validation: Check the configuration of manifest.json and pages.json for correct settings.
  • Easycom Configuration Analysis: Validate the easycom configuration in pages.json to ensure correct component referencing.
  • Compilation Output Inspection: Inspect the compiled output to confirm that components are correctly placed in the appropriate分包.
  • Use Case: For a uni-app project with分包, this Skill can help determine why certain uni_modules are included in the main package and provide recommendations for resolution.

Quick Start

Use the $uniapp-subpackage-uni-modules skill to check why the uni_modules in this uni-app project are mistakenly included in the main package.

Frequently Asked Questions about uniapp-subpackage-uni-modules

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

FAQPage Schema
Why are uni_modules mistakenly included in the main package in uni-app subpackage scenarios?▼

uni_modules are mistakenly included in the main package due to misconfigurations in manifest.json, pages.json, easycom settings, or incorrect component placement within the project structure.

How do I diagnose uni-app subpackage configuration issues for uni_modules?▼

Diagnose uni-app subpackage configurations by analyzing project structure, validating manifest.json and pages.json, checking easycom rules, and inspecting compiled output for correct component placement.

Does easycom configuration affect uni_modules placement in uni-app subpackages?▼

Yes, easycom configuration in pages.json directly affects uni_modules placement by determining how components are referenced, which dictates whether they compile into the main package or a subpackage.

What is the best way to check why uni_modules are in the main package?▼

The best way to check is to inspect the compiled output to confirm component placement and validate manifest.json, pages.json, and easycom configurations against the expected subpackage structure.

How do I fix uni_modules subpackage misplacement issues?▼

Fix misplacement by correcting the uni_modules directory structure, adjusting easycom component referencing in pages.json, and verifying subpackage settings in manifest.json.

What limitations exist when optimizing uni-app subpackages for uni_modules?▼

Optimization is limited by the project's structural constraints and the strictness of easycom referencing rules, requiring careful alignment of manifest.json, pages.json, and component directory placement.