Skip to content

fix(angular): import IonTab and IonTabBar directly instead of proxies barrel in standalone tabs - #31596

Open
rudrakshagarwal4200-ai wants to merge 1 commit into
ionic-team:mainfrom
rudrakshagarwal4200-ai:rudrakshagarwal4200-ai-patch-6
Open

rudrakshagarwal4200-ai wants to merge 1 commit into
ionic-team:mainfrom
rudrakshagarwal4200-ai:rudrakshagarwal4200-ai-patch-6

Conversation

@rudrakshagarwal4200-ai

Copy link
Copy Markdown

Summary

Fixes #31594.

In packages/angular/src/standalone/navigation/tabs.ts, IonTabs was importing IonTabBar and IonTab from ../directives/proxies. Because directives/proxies is the barrel that re-exports every component proxy, bundlers pulling IonTabs into the root route included all lazy-route Ionic components into the initial chunk, defeating standalone tree-shaking and component code-splitting.

Fix

Import IonTab from ../directives/ion-tab and IonTabBar from ../directives/ion-tab-bar directly, matching per-component entry points and preventing the entire proxies barrel from bundling into initial route chunks.

@vercel

vercel Bot commented Oct 17, 2026

Copy link
Copy Markdown

@rudrakshagarwal4200-ai is attempting to deploy a commit to the Ionic Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the package: angular @ionic/angular package label Oct 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

package: angular @ionic/angular package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: IonTabs (standalone) imports the directives/proxies barrel, so every component lands in the initial chunk

1 participant