Official adapter

knext is built on the official Next.js Deployment Adapter API — not a reverse-engineered runtime. The adapter is a small object implementing the official NextAdapter shape, shipped as a package export so any app (and the official compatibility harness) can point at it.

The adapter object

The knext adapter lives in @getknext/core and is exported at @getknext/core/adapter. Its default export is a NextAdapter:

const adapter: NextAdapter = {
  name: 'knext-adapter',
  modifyConfig(config, { phase }) {
    // forces output: 'standalone' on phase-production-build
  },
  async onBuildComplete(ctx) {
    // logs output counts + uploads static artifacts to object storage (keyed by buildId)
  },
};
export default adapter;

• modifyConfig forces output: 'standalone' during the production build.
• onBuildComplete uploads the build's static artifacts to the configured object store, keyed by buildId.

Wiring it into an app

On Next.js 16.2 and later, adapterPath is top-level configuration:

export default {
  adapterPath: '@getknext/core/adapter',
};

You can also point adapterPath at a thin local re-export file if you want the adapter contract visible at the app boundary:

import adapter from '@getknext/core/adapter';
export default adapter;

This is the same pattern used by the example apps in the knext repo, and by this docs site (the dogfood target).

Verified against the official suite

knext validates the adapter against the official Next.js compatibility suite: the vercel/next.js deploy-mode e2e harness runs through knext's lifecycle scripts and passes 778 tests with zero failures on the Node runtime, re-verified nightly (Next.js v16.2.0). A fast smoke gate additionally runs a Node + Bun matrix on every change.