Building for Production

Overview

Gridfinity Builder uses Vite to create optimized production builds with TypeScript compilation, code splitting, tree-shaking, and minification.

Build Process

Run TypeScript compiler

First, TypeScript compiles your code and checks for type errors:

tsc -b

This step:

Type-checks all .ts and .tsx files
Generates declaration files if needed
Validates TypeScript configuration

Build with Vite

Create the production bundle:

npm run build

yarn build

pnpm build

The build script runs:

"build": "tsc -b && vite build"

Verify the build

Check the build output in the dist/ directory:

ls -lh dist/

You should see:

index.html - Entry HTML file
assets/ - Bundled JS, CSS, and chunks
WASM files (manifold-3d)
PWA assets (service worker, manifest)

Build Output

The production build creates an optimized dist/ directory:

dist/
├── index.html                    # Entry point
├── assets/
│   ├── index-[hash].js          # Main bundle (code-split)
│   ├── index-[hash].css         # Compiled Tailwind CSS
│   ├── manifold-[hash].wasm     # Manifold WASM module
│   └── [chunk]-[hash].js        # Code-split chunks
├── icons/
│   ├── icon-192.png
│   └── icon-512.png
├── manifest.webmanifest          # PWA manifest
└── sw.js                         # Service worker

Optimization Features

Code splitting - Lazy-loaded routes and components
Tree shaking - Unused code eliminated
Minification - JavaScript and CSS compressed
Asset hashing - Cache-busting file names
WASM optimization - Manifold 3D module bundled efficiently
PWA caching - Service worker for offline support

Preview Production Build

Test the production build locally before deployment:

npm run preview

yarn preview

pnpm preview

This starts a local static file server:

➜  Local:   http://localhost:4173/
➜  Network: http://192.168.1.100:4173/

The preview server uses port 4173 by default, different from the dev server (5173).

Build Configuration

The build is configured in vite.config.ts:

export default defineConfig({
  plugins: [
    react(),
    tailwindcss(),
    VitePWA({
      registerType: 'prompt',
      includeAssets: ['icons/*.png', 'icons/*.svg'],
      manifest: {
        name: 'Gridfinity Builder',
        short_name: 'Gridfinity',
        description: 'Browser-based parametric CAD for Gridfinity',
        theme_color: '#0a0a0f',
        background_color: '#0a0a0f',
        display: 'standalone',
      },
      workbox: {
        globPatterns: ['**/*.{js,css,html,wasm,woff2}'],
        maximumFileSizeToCacheInBytes: 10 * 1024 * 1024,
      },
    }),
  ],
  optimizeDeps: {
    exclude: ['manifold-3d'],
  },
});

Key Configuration

Option	Purpose
`@vitejs/plugin-react`	Fast Refresh, JSX transform
`@tailwindcss/vite`	Tailwind CSS processing
`vite-plugin-pwa`	Service worker generation
`optimizeDeps.exclude`	Exclude Manifold WASM from pre-bundling

Deployment

Static Hosting

The dist/ folder can be deployed to any static hosting service:

# Install Vercel CLI
npm i -g vercel

# Deploy
vercel --prod

# Install Netlify CLI
npm i -g netlify-cli

# Deploy
netlify deploy --prod --dir=dist

# Build
npm run build

# Deploy to gh-pages branch
npx gh-pages -d dist

# Build
npm run build

# Upload to S3
aws s3 sync dist/ s3://your-bucket-name/

Server Requirements

Ensure your server is configured correctly for Single Page Applications (SPAs).

Required configurations:

MIME types - Serve .wasm files with correct MIME type:
application/wasm

Fallback routing - All routes should serve index.html (for client-side routing): Nginx:

location / {
  try_files $uri $uri/ /index.html;
}

Apache (.htaccess):

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.html [L]

HTTPS - Required for PWA installation and service workers

CORS headers - If serving WASM from CDN:

Access-Control-Allow-Origin: *
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin

Environment Variables

Vite exposes environment variables prefixed with VITE_:

# .env.production
VITE_API_URL=https://api.example.com
VITE_ANALYTICS_ID=UA-XXXXXXX

Access in code:

const apiUrl = import.meta.env.VITE_API_URL;

Build Optimization Tips

Reduce bundle size

Analyze bundle:

npm install -D rollup-plugin-visualizer

Add to vite.config.ts:

import { visualizer } from 'rollup-plugin-visualizer';

plugins: [
  visualizer({ open: true, filename: 'bundle-analysis.html' })
]

Run npm run build to generate an interactive bundle analysis.

Enable compression

Add Brotli/Gzip compression:

npm install -D vite-plugin-compression

import viteCompression from 'vite-plugin-compression';

plugins: [
  viteCompression({ algorithm: 'brotliCompress', ext: '.br' }),
  viteCompression({ algorithm: 'gzip', ext: '.gz' })
]

Split vendor chunks

Separate third-party libraries for better caching:

build: {
  rollupOptions: {
    output: {
      manualChunks: {
        'react-vendor': ['react', 'react-dom'],
        'three-vendor': ['three'],
        'manifold-vendor': ['manifold-3d'],
      },
    },
  },
}

Optimize WASM loading

The Manifold WASM module is large (~5MB). Ensure:

Lazy load - Only load when needed (already implemented via Web Worker)
Cache - Service worker caches WASM file
CDN - Serve from CDN with Brotli compression

Preload - Add to index.html:

<link rel="preload" href="/assets/manifold.wasm" as="fetch" crossorigin>

Troubleshooting

Build fails with TypeScript errors

TypeScript compilation must succeed before Vite builds:

# Check for type errors
tsc --noEmit

# Fix or skip type checking (not recommended)
vite build --mode production

WASM module not loading in production

Ensure your server:

Serves .wasm with MIME type application/wasm
Has correct CORS headers if WASM is on a different origin
Uses HTTPS (required for SharedArrayBuffer)

Test locally:

npm run preview
# Open browser console and check for WASM errors

Service worker not updating

Clear the service worker cache:

# Increment version in vite.config.ts
manifest: {
  version: '1.0.1',  // Bump this
}

In browser DevTools:

Application → Service Workers → Unregister
Application → Storage → Clear site data
Hard refresh (Ctrl+Shift+R)

Large bundle size

If the bundle is unexpectedly large:

# Analyze with visualizer
npm install -D rollup-plugin-visualizer
npm run build

Common causes:

Unused dependencies (check package.json)
Large assets not lazy-loaded
Duplicate dependencies (check with npm ls <package>)

CI/CD Example

GitHub Actions

.github/workflows/deploy.yml

name: Build and Deploy

on:
  push:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    
    steps:
      - uses: actions/checkout@v4
      
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      
      - name: Install dependencies
        run: npm ci
      
      - name: Build
        run: npm run build
      
      - name: Deploy to GitHub Pages
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./dist

Setup

Contributing

Overview

Build Process

Build Output

Optimization Features

Preview Production Build

Build Configuration

Key Configuration

Deployment

Static Hosting

Server Requirements

Environment Variables

Build Optimization Tips

Troubleshooting

CI/CD Example

GitHub Actions

Next Steps

Local Setup

Docker Development

​Overview

​Build Process

​Build Output

​Optimization Features

​Preview Production Build

​Build Configuration

​Key Configuration

​Deployment

​Static Hosting

​Server Requirements

​Environment Variables

​Build Optimization Tips

​Troubleshooting

​CI/CD Example

​GitHub Actions

​Next Steps

Local Setup

Docker Development

Overview

Build Process

Build Output

Optimization Features

Preview Production Build

Build Configuration

Key Configuration

Deployment

Static Hosting

Server Requirements

Environment Variables

Build Optimization Tips

Troubleshooting

CI/CD Example

GitHub Actions

Next Steps