use vitepress fork with memory workaround #20

	name: Deploy VitePress site to Pages

	on:
	push:
	branches: [master]

	# Allows you to run this workflow manually from the Actions tab
	workflow_dispatch:

	# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
	permissions:
	contents: read
	pages: write
	id-token: write

	# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
	# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
	concurrency:
	group: pages
	cancel-in-progress: false

	jobs:
	# Build job
	build:
	runs-on: ubuntu-latest
	steps:
	- name: Checkout scrapiyard
	uses: actions/checkout@v4
	with:
	repository: ProjectIgnis/scrapiyard
	path: scrapiyard
	- name: Checkout scrapi-book
	uses: actions/checkout@v4
	with:
	path: main
	- name: Setup Node
	uses: actions/setup-node@v3
	with:
	node-version: 20
	cache: npm
	cache-dependency-path: ./main
	- name: Setup Pages
	uses: actions/configure-pages@v3
	- name: Build Site
	working-directory: main
	run: \|-
	npm ci
	npm run create-api-pages
	npm run docs:build
	- name: Upload artifact
	uses: actions/upload-pages-artifact@v2
	with:
	path: main/docs/.vitepress/dist

	# Deployment job
	deploy:
	environment:
	name: github-pages
	url: ${{ steps.deployment.outputs.page_url }}
	needs: build
	runs-on: ubuntu-latest
	name: Deploy
	steps:
	- name: Deploy to GitHub Pages
	id: deployment
	uses: actions/deploy-pages@v2

Provide feedback