Hello Teable Support,
I’m updating an app to improve security and keep its dependencies current.
The main blocker is upgrading Next.js 16.3.5 to 16.4.3, together with eslint-config-next. The current dependency audit reports 11 Next.js advisories: 3 critical, 2 high, 5 moderate, and 1 low. Their applicability to this app has not been established, but I would like to move to a patched release.
During upgrade attempts, the installed Next.js package changed to 16.4.3, but the platform-managed launcher and server process remained on 16.3.5. The Preview then returned HTTP 500 with:
TypeError: routeModule.ensureInstrumentation is not a function
Restoring 16.3.5 recovered the Preview.
An isolated next build --webpack using 16.4.3 and React 19.3.1 completed successfully after excluding copied Preview-only instrumentation. This supports build compatibility, but does not verify the platform’s Preview tooling or a live 16.4.3 runtime. The isolated build also had external-dependency file-tracing warnings and was not deployed.
Could you please:
- Confirm which patched Next.js versions the platform currently supports.
- Confirm how app builders should request future framework restarts.
Thank you.