Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.withnubo.com/llms.txt

Use this file to discover all available pages before exploring further.

For any Node app (Express API, Discord bot, Next.js, plain TypeScript service), Nubo needs three things:
  1. A package.json at the repo root.
  2. A start script that boots your server.
  3. Your server reads the port from process.env.PORT.
If those are in place, skip to Deploy.

​
Quick start

mkdir hello-node && cd hello-node
npm init -y
npm install express
server.js:
server.js
import express from "express";

const app = express();
app.get("/", (_, res) => res.send("Hello from Node on Nubo!"));

const port = process.env.PORT ?? 3000;
app.listen(port, () => console.log(`listening on :${port}`));
Add "type": "module" and a start script to package.json:
package.json
{
  "type": "module",
  "scripts": {
    "start": "node server.js"
  },
  "dependencies": {
    "express": "^4.21.0"
  }
}
Local test, then push: 
PORT=3000 npm start
git init && git add . && git commit -m "init"
git remote add origin git@github.com:yourname/hello-node.git
git push -u origin main

​
Deploy

1

Open the New Frame modal

In your Nubo dashboard, open the Project and Space you want, then hit + Frame.
2

Pick the repo and branch

Connect your GitHub repo and choose the branch Nubo should watch.
3

Confirm the port

The port your app listens on. Matches the PORT value you read in code.
4

Deploy

Hit deploy. Watch the build in the Logs tab.

​
Package managers

Nubo auto-picks based on your lockfile:
Commit this lockfileGet this manager
package-lock.jsonnpm
pnpm-lock.yamlpnpm
yarn.lockyarn
bun.lockb or bun.lockbun
Commit your lockfile. Without one, Nubo falls back to npm. This isn’t fatal but builds are slower and less deterministic.

​
TypeScript apps

Add a build script that produces JavaScript and a start script that runs it:
package.json
{
  "scripts": {
    "build": "tsc -p .",
    "start": "node dist/server.js"
  }
}
Nubo runs npm run build automatically when a build script exists.

​
Things that trip people up

  • No start script. Nubo will try node index.js as a fallback. If your entry isn’t index.js, set "main" in package.json or add a start script.
  • Hardcoded port. Read process.env.PORT, don’t write 3000 directly.
  • Listening on localhost. Use the default Express behavior (app.listen(port)) or bind explicitly to 0.0.0.0.
  • Native modules. node:22-slim doesn’t ship build toolchains. Prefer packages with prebuilt binaries, or switch to the Paketo builder.

​
Framework guides

React (Vite)

Single-page app with a Vite build
https://mintcdn.com/nuboinc/Tvg6ZQ2e7v9l7UTE/icons/discordjs.svg?fit=max&auto=format&n=Tvg6ZQ2e7v9l7UTE&q=85&s=2da943f168b323473aef6dd3f8a48003

Discord.js

Long-running bot, no HTTP listener

​
How the build works

This guide uses the Node.js pack of Raypacks, Nubo’s default builder. It installs your deps, runs your build script if you have one, and ships on node:22-slim (or oven/bun:slim for bun). For control beyond what the pack offers, switch the Frame’s Builder to Paketo in Frame Settings.