Refactor middleware exports to named exports for consistency

[devkiran]

Summary by CodeRabbit

• Refactor
  • Updated internal code structure for middleware modules to improve module export consistency across the application.

[vercel]

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

Project	Deployment	Preview	Updated (UTC)
dub	Ready	Preview	Oct 17, 2025 9:59am

[coderabbitai]

Walkthrough

Converts middleware functions across the /apps/web/lib/middleware/ directory from default exports to named exports. Updates include modifying individual middleware exports, the barrel export index, and corresponding import statements in dependent files to use named import syntax.

Changes

Cohort / File(s)	Change Summary
Middleware function exports apps/web/lib/middleware/admin.ts, apps/web/lib/middleware/api.ts, apps/web/lib/middleware/axiom.ts, apps/web/lib/middleware/create-link.ts, apps/web/lib/middleware/embed.ts, apps/web/lib/middleware/link.ts, apps/web/lib/middleware/new-link.ts, apps/web/lib/middleware/partners.ts, apps/web/lib/middleware/workspaces.ts	Changed function exports from default to named exports (e.g., export default function → export function)
App middleware imports apps/web/lib/middleware/app.ts	Converted function export to named export and updated internal imports for EmbedMiddleware, NewLinkMiddleware, and WorkspacesMiddleware from default to named imports
Barrel export and consumer update apps/web/lib/middleware/index.ts, apps/web/middleware.ts	Updated barrel exports to remove default aliasing (e.g., export { default as AdminMiddleware } → export { AdminMiddleware }); updated PartnersMiddleware import in middleware.ts from default to named import

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

This is a consistent, homogeneous refactoring of export/import patterns with no logic or behavior changes. All modifications follow the same straightforward pattern across multiple files, making verification quick.

Poem

🐰 From default to named, the exports now stand clear,
No shadows of ambiguity, each function shines here,
The imports align, a cohesive parade,
Where refactoring magic has beautifully played! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Refactor middleware exports to named exports for consistency" directly and accurately describes the main change across the pull request. The changeset consistently converts all middleware modules from default exports to named exports, affecting 10 individual middleware files, the index.ts barrel export, and the middleware.ts import consumer. The title is concise (8 words), specific, and clearly communicates the primary architectural change without noise or vague terminology. A developer scanning commit history would immediately understand the refactoring's purpose and scope.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove-default-exports-2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46a8b5a and 268e164.

📒 Files selected for processing (12)

• apps/web/lib/middleware/admin.ts (1 hunks)
• apps/web/lib/middleware/api.ts (1 hunks)
• apps/web/lib/middleware/app.ts (1 hunks)
• apps/web/lib/middleware/axiom.ts (1 hunks)
• apps/web/lib/middleware/create-link.ts (1 hunks)
• apps/web/lib/middleware/embed.ts (1 hunks)
• apps/web/lib/middleware/index.ts (1 hunks)
• apps/web/lib/middleware/link.ts (1 hunks)
• apps/web/lib/middleware/new-link.ts (1 hunks)
• apps/web/lib/middleware/partners.ts (1 hunks)
• apps/web/lib/middleware/workspaces.ts (1 hunks)
• apps/web/middleware.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (12)

apps/web/lib/middleware/embed.ts (1)

4-4: LGTM! Clean refactoring to named export.

The conversion from default export to named export is straightforward and improves consistency across the middleware layer.

apps/web/lib/middleware/admin.ts (1)

7-7: LGTM! Consistent refactoring.

The named export pattern improves code discoverability and aligns with the PR's consistency goal.

apps/web/lib/middleware/partners.ts (1)

19-19: LGTM! Consistent with the refactoring pattern.

The named export enhances import clarity and follows the established pattern across the middleware directory.

apps/web/lib/middleware/axiom.ts (1)

4-4: LGTM! Clean conversion to named export.

The refactoring maintains the function signature and logic while improving module consistency.

apps/web/lib/middleware/link.ts (1)

41-41: LGTM! Consistent refactoring.

The named export pattern is properly applied, maintaining all existing functionality.

apps/web/lib/middleware/new-link.ts (1)

7-7: LGTM! Proper named export conversion.

The refactoring is consistent with the PR objective and maintains the function's signature and behavior.

apps/web/lib/middleware/create-link.ts (1)

5-5: LGTM! Clean refactoring to named export.

The conversion maintains all existing functionality while improving code consistency.

apps/web/lib/middleware/api.ts (1)

4-4: LGTM! Clean conversion to named export.

The change from default export to named export is correct and aligns with the PR objective for consistency.

apps/web/lib/middleware/app.ts (2)

12-12: LGTM! Clean conversion to named export.

The change from default export to named export for AppMiddleware is correct and aligns with the PR objective.

---

3-4: All middleware files correctly export named exports — verification complete.

All three middleware functions are properly exported as named exports:

• embed.ts exports export function EmbedMiddleware
• new-link.ts exports export async function NewLinkMiddleware
• workspaces.ts exports export async function WorkspacesMiddleware

The named imports in app.ts (lines 3-4 and line 10) match the exported function names exactly. No issues found.

apps/web/middleware.ts (1)

19-19: No issues found — PartnersMiddleware is correctly exported as a named export.

Verification confirms that apps/web/lib/middleware/partners.ts exports PartnersMiddleware as a named export (line 19: export async function PartnersMiddleware), and the import statement in middleware.ts correctly uses named import syntax. No default export exists.

apps/web/lib/middleware/index.ts (1)

1-6: All middleware exports verified correctly.

Verification confirms:

• ✅ All 6 source middleware files (admin.ts, api.ts, app.ts, axiom.ts, create-link.ts, link.ts) export functions as named exports using export function or export async function
• ✅ Barrel export in index.ts correctly re-exports all 6 middleware as named exports
• ✅ Consumer in apps/web/middleware.ts correctly imports using named imports from @/lib/middleware
• ✅ No default exports found in any middleware files

The code changes are correct and properly structured.