seenode™
Deploy
Deploy an Angular SPA

Deploy an Angular SPA

Deploy an Angular SPA as a seenode static site. Build, publish the folder that contains index.html, SPA routing on by default.

Last updated September 18, 2026

New to seenode? Start free: 7-day trial, no credit card. Static sites are $0.

This guide deploys an existing Angular SPA as a static site. seenode runs your build and serves the files. You do not need Express or a start command.

Note (Need a Node server?)

If the app is an API or must run Node at request time, create a web service instead and follow Express.

Prerequisites

  • A seenode account
  • Git configured on your machine
  • An Angular CLI project that builds to a folder containing index.html

Deploy on seenode

  1. Push to Git

    Commit the project and push it to GitHub or GitLab.

  2. Create a Static site

    From the dashboard, create a Static site and connect the repository.

  3. Build settings

    • Language: Node
    • Build command: npm install && npm run build

    • Publish directory: the folder that contains index.html after the build. Check angular.json outputPath (often dist/<project> or dist/<project>/browser ).

    • Client-side routing (SPA): leave on so Angular Router deep links work

  4. Create

    Create the site and watch Logs until the build finishes.

Troubleshooting

  • 404 on client routes: leave SPA routing on, or add a rewrite /* → /index.html on Routing.
  • Empty site: publish directory must be the folder with index.html, not dist if Angular nested another folder.
  • Missing src/styles.css: Angular CLI references it from angular.json by default. Add the file or update the styles array.

Starting from scratch?

Follow the official Angular docs, then the steps above. An older Express template: example-angular-with-express.

Next steps

Static sites

Publish directory, SPA routing, and headers.

Custom domain

Point your own domain at the site.

Environment variables

Build-time keys for static sites.