Build for production

A JOPS app needs no compilation: the files you develop are the files you ship. The build step only collects them into a clean folder for deployment.

Build

1. Make sure the vendored library matches the installed version:

   npx jops-core update

2. Build:

   npm run build

   npx jops-core init added this script to package.json; it runs npx jops-core build.

3. Upload the dist/ folder to your server or static host.

What ends up in dist/

The build copies your project into dist/ and leaves out what the browser doesn’t need:

• node_modules/, .git/ and an earlier dist/
• package.json, package-lock.json, .gitignore, .npmrc
• Markdown files (.md), npm tarballs (.tgz) and logs (.log)

Everything else (index.html, lib/, src/, assets/) is copied as is. dist/ is replaced on every build.

If lib/jops-core.min.js differs from the version installed in node_modules, the build prints a warning and suggests running npx jops-core update first.

Deploying

dist/ is a set of static files: any web server or static host can serve it (Nginx, Apache, IIS, S3 with CloudFront, GitHub Pages and similar). Routes live in the URL hash (#home, #features), so the server never sees them and needs no rewrite rules.

Caution

The templates use root-based paths (/src/..., /lib/...), so serve the dist/ folder as the root of a site or subdomain. Apps loading the library from the CDN with ./ paths also work in a subfolder. See Installation.

Tip

Browsers and CDNs cache static files. After a deployment, users may keep an old copy of a file for a while; plan your cache headers accordingly.

Other platforms

jops-core build is for web projects. Other project types use their own packaging tools:

Hybrid mobileCordova and Capacitor ship the web folder as is: use cordova build or npx cap sync.

ElectronPackage the desktop app with npm run make.

Next.jsThe JOPS app is part of your Next.js build and deployment.