Frameworks

Frameworks

Stackap recognizes a project by its dependencies, generates a container for it, and tells you exactly which frameworks that covers.

Stackap recognizes a project by its dependencies, generates a container for it, and tells you exactly which frameworks that covers.

The pages below describe what is recognized and how, what has been tested with a real build, and what has not. A framework is listed only when the platform handles it, and untested support is labeled as untested.

Pages in this section

• Next.js: How Stackap detects a Next.js project, the container it generates, how public and secret variables are handled, and what has been measured.
• React: How a React app is served on Stackap: static single-page builds with client-side routing work, server components and server rendering do not.
• Vite and React single-page apps: How Stackap builds Vite, Create React App, Vue CLI and Parcel single-page apps and serves them from nginx with a fallback to index.html.
• Astro: How Stackap builds a static Astro site and serves it from nginx with real 404 pages, and why Astro with a server adapter is not treated as static.
• Remix: Stackap does not recognize Remix by name. What its detection does with a Remix project, when a start script lets it run as Node, and what is untested.
• Nuxt: Stackap does not recognize Nuxt by name. Why a Nuxt project skips the static path, how a start script changes that, and the untested caveats.
• SvelteKit: Stackap does not recognize SvelteKit by name. How its detection treats the dependency, using the Node adapter with a start script, and what is untested.
• Gatsby: How Stackap builds a Gatsby site and serves its public folder from nginx with real 404s, what Gatsby features need a server, and what is untested.
• Docusaurus: How Stackap builds a Docusaurus documentation site and serves the build folder with a real 404 page, and the baseUrl setting that most often breaks it.
• Eleventy: How Stackap builds an Eleventy site and serves the _site folder, and why a project with no build script in package.json is not recognized.
• VitePress: How Stackap builds a VitePress site from .vitepress/dist, and why the default docs:build script name means you must add a build script first.
• Node.js: How Stackap runs a Node.js app that has a start script: the generated image, the PORT contract, health checks and what is not supported.
• Plain static sites: How Stackap serves a repository that is already a finished site, with an index.html at the root and nothing to build, and what is stripped from the image.
• Python: Stackap has no Python support of its own. A Python app can run only if you provide a Dockerfile that listens on PORT, which is untested.

Last updated 2026-10-03.