Frameworks

Nuxt on Stackap

Q: What is the quickest way to try?

Write a small Dockerfile for your Nuxt app that listens on PORT , push it to a test project, and read the logs.

Stackap does not recognize Nuxt yet: a project that depends on nuxt skips the static path, and it needs a start script or a Dockerfile of its own to run.

How Stackap recognizes Nuxt

A dependency named nuxt keeps a project off the static-site path, because a Nuxt app is built to render on a server. After that, detection looks for an index.html at the repository root, finds none, and then looks for a start script. A fresh Nuxt project does not usually define one; its scripts are typically build, dev and preview. With none, the build is refused with a reason.

What Stackap builds

There are two honest routes. The first is to add a start script that runs the production server Nuxt produces, so that Stackap treats the project as a Node app. The second is to bring a Dockerfile that builds and starts the app, which Stackap uses as it is.

Nuxt can also generate a fully static site. A static output step that writes an index.html into .output/public is not on the folder list Stackap searches, so a statically generated Nuxt site needs its output moved to a folder the list does contain, such as dist, and the project would still need to avoid the nuxt dependency check, which is not something we have worked out.

In every case the app must listen on PORT and answer a health request.

What a Nuxt project needs

Either a start script or your own Dockerfile.
The production server bound to PORT, not a fixed number.
A health route.
Public and secret values separated: only prefixed public values belong in client code.

Verification status

Verification pending. No Nuxt project has been built or served on Stackap, and the static-generation route above is unresolved, not merely untried.

The generic Node path and the Dockerfile path are tested with other projects.

Early-access scope

Nuxt is not a supported framework today.
A statically generated Nuxt site does not fit the static path as detection stands, because the nuxt dependency excludes it.
Nitro features aimed at edge or serverless runtimes have no equivalent.
Only HTTP servers are supported, with no persistent disk.

Questions

Why not just add Nuxt to the list?

Because adding it without building a real project would be a claim we cannot back. The list grows when a project of that kind has been served.

What is the quickest way to try?

Write a small Dockerfile for your Nuxt app that listens on PORT, push it to a test project, and read the logs.

Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.

Ask for an invitation

Last updated 2026-10-03.