# Assistance upgrading Next.js

**URL:** https://community.teable.ai/t/assistance-upgrading-next-js/394
**Category:** Teable Discussions
**Created:** [October 29, 2026, 2:02pm UTC](https://community.teable.ai/t/assistance-upgrading-next-js/394 "2026-10-29T14:02:02Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Alex](https://community.teable.ai/user_avatar/community.teable.ai/alex/32/248_2.png) [@Alex](https://community.teable.ai/u/Alex)
#### Post date: [October 29, 2026, 2:02pm UTC](https://community.teable.ai/t/assistance-upgrading-next-js/394/1 "2026-10-29T14:02:02Z")

</div>

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:

1. Confirm which patched Next.js versions the platform currently supports.
2. Confirm how app builders should request future framework restarts.

Thank you.
