Skip to content

???????????????? #262

@yeyixiang2007

Description

@yeyixiang2007

What to build

Reduce frontend bundle cost and establish an enforceable guardrail so future changes do not silently bloat the application. This slice should target the biggest current bundle contributors, improve chunking, and define a lightweight build-size check that maintainers can rely on.

Acceptance criteria

  • The build no longer emits the current chunk-size warning for the targeted oversized path, or the remaining exception is explicitly justified.
  • At least one meaningful code-splitting or lazy-loading improvement lands for a high-cost frontend path.
  • The project gains a simple repeatable way to track build-size regressions.
  • Verification records bundle-size before/after for the targeted chunk(s).

Blocked by

None - can start immediately

Metadata

Metadata

Assignees

No one assigned

    Labels

    AFKAway-from-keyboard: 可独立完成enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions