As Forge adoption grows, many developers are moving away from monolithic frontend structures in favor of modular architectures. These modular approaches offer significant advantages in terms of feature velocity, dependency management, and long-term maintainability—especially for complex or large-scale apps.

However, the current hard limit of 10 resources per manifest.yml file presents a significant constraint. During migrations from Connect to Forge, teams often exceed this limit early in the process, particularly when separating functionality into smaller, purpose-specific frontend bundles (e.g., per iframe or feature).

This limitation forces developers to group unrelated modules into shared resources, which:

• Increases coupling between components

• Reduces deployment resilience

• Hinders maintainability

• Slows down development workflows

Request:
We propose increasing the maximum number of resources allowed in a single manifest.yml file. A higher threshold would better support scalable app architectures and align with the direction many Forge apps are taking.

Impact:
This change would benefit:

• Teams adopting modular frontend strategies

• Apps transitioning from Connect to Forge

• Multi-team or enterprise-grade development pipelines

• Compliance with upcoming changes to Marketplace programs (e.g., revenue share requirements)