Rename lib/proxy.ts to lib/backendProxy.ts #232

New issue

Closed

opened 2026-09-22 20:55:13 +00:00 by aaperis · 1 comment

aaperis commented

2026-09-22 20:55:13 +00:00

(Migrated from github.com)

Description

Next.js 16 deprecated the filename middleware.ts in favor of proxy.ts(introduced in #231) for the name of a middleware because the former was deemed confusing. The new name is fixed by the framework.

It so happens that we previously introduced the file lib/proxy.ts that contains the backend proxy logic of the webapp. Although keeping both files with the same name does not break functionality since they are in well-separated places, it would be clearer if they had different names.

AC:

rename lib/proxy.ts to lib/backendProxy.ts and related imports.
verify that nothing breaks

## Description Next.js 16 deprecated the filename `middleware.ts` in favor of `proxy.ts`(introduced in #231) for the name of a middleware because the former was deemed confusing. The new name is fixed by the framework. It so happens that we previously introduced the file `lib/proxy.ts` that contains the backend proxy logic of the webapp. Although keeping both files with the same name does not break functionality since they are in well-separated places, it would be clearer if they had different names. AC: - rename `lib/proxy.ts` to `lib/backendProxy.ts` and related imports. - verify that nothing breaks

aaperis commented

2026-09-22 21:20:23 +00:00

(Migrated from github.com)