feat: Automatic tree-shaking of messages (experimental)

[amannn]

Resolves #1 (but very, very WIP to experiment for now)

TODO

• Implementation
  • Turbopack: emit/collect vercel/next.js#91100
  • Compiler orchestration
    • Manifest loader only has a single compile pass. Can we do something similar to integrate with extraction loader?
    • Offload more to SWC / Rust? Maybe a single SWC plugin that returns all analysis (useExtracted, deps, 'use client', …)
    • Can we emit extractor and tree shaking result at same time to avoid redundant work?
  • API
    • Should we add a lower-level API? The usage is slightly misleading, because not everything below the provider is collected, but everything that is imported into the module. E.g. import manifest from 'next-intl/client-manifest?path=optional' with {type: 'macro'} would be another candidate, but not sure if the verbosity is worth it (or if it's even clearer). It's surely more explicit, but useExtracted is already implicitly subject to AST transforms—so not sure if we need to do it here.
    • Pages Router?
    • Any way to easily cut off server messages without more work?
  • Edge cases
    • Solution for error.tsx
    • fix: Barrel file tree-shaking #2262
    • Check Next.js docs thoroughly for other use cases to consider
    • Configurable tsconfig? (ref) — forward this
    • Test what happens where there are syntax errors.
  • Rework implementation / deslop
  • Performance
• Tests
  • Can we reuse this for an integration test?
• First user testing
•  Docs
  • A playground for toggling layout boundaries?

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
next-intl-docs	Ready	Preview, Comment	Feb 23, 2026 4:28pm
next-intl-example-app-router	Ready	Preview, Comment	Feb 23, 2026 4:28pm
next-intl-example-app-router-without-i18n-routing	Ready	Preview, Comment	Feb 23, 2026 4:28pm