Bug: Next.js 16 deprecated middleware.ts causing broken proxy.accessibility.test.ts

[Aamod007]

Description

Next.js 16.2.7 has deprecated the middleware.ts file convention in favor of proxy.ts. During the build process, the following warning is emitted:
⚠ The middleware file convention is deprecated. Please use proxy instead.

Additionally, the test suite currently contains proxy.accessibility.test.ts which explicitly attempts to import from ./proxy. Because the file has not yet been renamed from middleware.ts, the npm run typecheck and npm run test pipelines fail with TS2307: Cannot find module './proxy'.

Impact

• Build pipelines are cluttered with deprecation warnings.
• CI/CD pipelines fail entirely due to the missing module import in the test suite.

Suggested Fix

1. Rename middleware.ts in the project root to proxy.ts.
2. Ensure proxy.accessibility.test.ts properly imports and tests the renamed module.

[Kokila-chandrakar]

/claim

[github-actions]

🎉 Assigned! Welcome to the project, @Kokila-chandrakar.

⏳ Reminder: You have 2 days to submit a Pull Request. After 2 days of inactivity, you will be automatically unassigned to give others a chance (as per our GSSoC anti-hoarding policy).

💡 Please read CONTRIBUTING.md if you haven't already.

Happy coding! 🚀