Installation from Source
Build and install InSpectres VTT directly from the repository source code. Use this if you want to:
- Contribute changes back to the project
- Test unreleased features
- Develop custom extensions
Prerequisites
- Git (to clone the repository)
- Node.js 22 or later (download here)
- npm (comes with Node.js)
- A Foundry data folder
Installation Steps
1. Clone the Repository
git clone https://github.com/phaedrus1992/inspectres-vtt.git
cd inspectres-vtt
2. Install Dependencies
cd foundry
npm install
3. Build the System
npm run build
You should see output like:
vite v5.x.x building for production...
✓ 1234 modules transformed.
dist/inspectres.js 1.2 MB
4. Link (or Copy) to Foundry Systems Folder
Option A: Create a symbolic link (recommended for development)
This way, you can edit source code and rebuild without re-copying files.
# From the inspectres-vtt directory:
ln -s "$(pwd)/foundry/dist" "<path-to-foundry>/systems/inspectres"
Replace <path-to-foundry> with your actual Foundry systems directory:
- Windows PowerShell (Admin):
mklink /D "C:\path\to\systems\inspectres" ".\foundry\dist" - Windows CMD (Admin):
mklink /D C:\path\to\systems\inspectres .\foundry\dist
Option B: Copy the dist folder
cp -r foundry/dist /path/to/foundry/systems/inspectres
After copying, your folder structure should look like:
systems/
inspectres/
inspectres.js
styles/
templates/
... (other files)
5. Launch Foundry and Activate the System
Same as the release installation — create a world, select InSpectres VTT as the system, and launch.
Development Workflow
While developing, you'll want to watch for changes and rebuild automatically:
# From the foundry/ directory:
npm run dev
This watches source files and rebuilds whenever you save. Then:
- Refresh the Foundry browser tab (or restart Foundry if you changed JSON/template files)
- Your changes are active
To run tests and type checks:
npm run check # Type check
npm run test # Run tests
npm run test:watch # Watch mode
Troubleshooting
"npm install" fails
- Make sure you're in the
foundry/subdirectory, not the repo root - Try
npm install --legacy-peer-depsif peer dependency errors occur - Check that Node.js 22+ is installed:
node --version
"npm run build" fails
- Check for TypeScript errors:
npm run check - Make sure all dependencies are installed:
npm install
Symlink not working (Windows)
- Run your terminal as Administrator
- Some antivirus software may block symlinks — try copying instead (Option B)
Changes aren't showing up in Foundry
- Did you run
npm run build(or havenpm run devwatching)? - Refresh the Foundry tab in your browser
- If changing JSON/templates, fully restart Foundry
- Check browser console for errors (F12)
Contributing
Once you've made changes and verified they work:
- Write tests for new functionality
- Run
npm run checkandnpm run test— fix any issues - Commit with a descriptive message
- Submit a pull request to the repository
See Contributing for detailed guidelines.
Next Steps
- Check Architecture to understand how the system is organized
- Run the test suite:
npm run test - Launch Foundry with your build and create a test world