SEAM is a vanilla JavaScript SPA served by a lightweight Node.js HTTP server — there is no bundler or build step required for JavaScript. The only build process you need to run is the Tailwind CSS compilation, which can run in watch mode alongside the server in a second terminal.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/TheSerchCp/SEAM/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before you start, make sure you have the following in place:- Node.js 18 or later — the
--watchflag used by thedevscript requires Node 18+. - A running backend API — SEAM expects a REST API at
http://localhost:3001/api/v1by default. Start your backend server before opening the app.
Installing dependencies
Clone the repository and install the dev dependencies (Tailwind CSS, PostCSS, and Nodemon):NPM scripts
All available scripts are defined inpackage.json:
| Script | Command | Purpose |
|---|---|---|
start | node server.js | Run the production-like server on port 3000, no auto-restart |
dev | node --watch server.js | Run the server with Node’s built-in file watcher; restarts on any .js change |
dev:watch | node --watch server.js | Alias for dev — identical built-in watch behaviour |
dev:nodemon | nodemon server.js | Run the server with Nodemon (watches server.js and js/**/*.js) |
build:css | node build-tailwind.mjs | One-shot Tailwind CSS build — reads css/tailwind-base.css, writes css/tailwind.css |
build:css:watch | tailwindcss -i ./css/tailwind-base.css -o ./css/tailwind.css --watch | Rebuild css/tailwind.css automatically on every template change |
Running for development
The recommended development workflow uses two terminals running in parallel — one for CSS watching and one for the server.Start the Tailwind CSS watcher
Open your first terminal and start the CSS watcher. It will rebuild You should see Tailwind confirm it is watching. Leave this terminal open.
css/tailwind.css every time you change a Tailwind class in any HTML or JavaScript file:Start the development server
Open a second terminal and start the Node.js server with the file watcher:The server starts on port 3000. Open http://localhost:3000 in your browser.
Open the app
Navigate to http://localhost:3000. The built-in server handles all SPA routing by falling back to
index.html for any path without a file extension, so hash-based navigation (#/home, #/usuarios, etc.) works out of the box.Changing the API base URL
SEAM reads the backend URL from a single file. Openjs/config/api.js and update the API_BASE constant to match your backend:
js/config/api.js
dev script will restart the server automatically, and all ApiClient calls will use the new base URL immediately.
Changing the server port
The port is defined as a constant at the top ofserver.js:
server.js
PORT to any available port and restart the server. Remember to update any backend CORS configuration if it whitelists the frontend origin explicitly.
One-shot CSS build
If you only need to compile CSS once (for example, before a deployment), run:build-tailwind.mjs uses PostCSS with @tailwindcss/postcss to process css/tailwind-base.css and write the output to css/tailwind.css. On success it prints: