Skip to content

fix: use relative paths for models and assets to support GitHub Pages… #7

fix: use relative paths for models and assets to support GitHub Pages…

fix: use relative paths for models and assets to support GitHub Pages… #7

Workflow file for this run

# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
name: Node.js CI + Deploy
on:
push:
branches: ["main"]
pull_request:
branches: ["main"]
# Need permissions for GitHub Pages
permissions:
contents: read
pages: write
id-token: write
jobs:
build:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [20.x]
steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
cache: 'npm'
- run: npm install
- run: npm run build --if-present
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: './dist' # ← change to your build output folder (dist, build, out, etc.)
deploy:
needs: build
runs-on: ubuntu-latest
if: github.ref == 'refs/heads/main' # Only deploy on push to main, not PRs
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4