This guide helps you resolve common setup issues with the Codebase Timeline Visualizer.
# Double-click setup.bat or run in PowerShell:
.\setup.bat# 1. Create virtual environment
python -m venv .venv
# 2. Activate virtual environment
.venv\Scripts\activate
# 3. Install Python dependencies
pip install -r requirements.txt
# 4. Run setup check
python check_setup.pySymptoms:
❌ Node.js/npm is not installed or not in PATH
Download from: https://nodejs.org/
Or install with: choco install nodejs
Solutions:
- Download from nodejs.org
- Run the installer
- Restart your terminal/command prompt
- Run setup check again
# Install Chocolatey (if not already installed)
# Visit: https://chocolatey.org/install
# Install Node.js
choco install nodejs
# Refresh environment
refreshenv
# Verify installation
node --version
npm --version- Find Node.js installation directory (usually
C:\Program Files\nodejs\) - Add it to your system PATH:
- Windows Search → "Environment Variables"
- System Properties → "Environment Variables"
- Edit "Path" variable
- Add:
C:\Program Files\nodejs\
- Restart terminal and run setup check
Symptoms:
❌ gitpython - No module named 'git'
❌ pydriller - No module named 'pydriller'
Solutions:
# Activate virtual environment
.venv\Scripts\activate
# Install dependencies
pip install -r requirements.txt
# Run setup check
python check_setup.py# Install dependencies globally
pip install -r requirements.txt
# Run setup check
python check_setup.py# Make sure you're using the virtual environment Python
.venv\Scripts\python.exe check_setup.pySymptoms:
❌ Git is not installed or not in PATH
Solutions:
- Download from git-scm.com
- Run the installer with default options
- Restart terminal
- Verify:
git --version
choco install git
refreshenv
git --versionSymptoms:
❌ Python 3.8 or higher is required
Solutions:
- Download from python.org
- Make sure to check "Add Python to PATH" during installation
- Restart terminal
- Verify:
python --version
# Use Python 3.8+ explicitly
py -3.8 --version
py -3.9 --version
py -3.10 --version# Using batch file
.\setup.bat
# Or manually
.venv\Scripts\python.exe check_setup.py# Activate virtual environment
.venv\Scripts\activate
# Test CLI
python -m cli.src.main --help
# Test analyzer (create a test repo first)
mkdir test-repo
cd test-repo
git init
echo "print('test')" > test.py
git add .
git commit -m "Test commit"
cd ..
python -m cli.src.main analyze ./test-repo# Start the server
python -m cli.src.main serve
# Open browser to http://localhost:3001The setup check verifies these files exist:
- ✅
requirements.txt - ✅
setup.py - ✅
README.md - ✅
backend/src/__init__.py - ✅
backend/src/analyzer.py - ✅
backend/src/exporter.py - ✅
backend/src/main.py - ✅
frontend/package.json - ✅
frontend/src/App.js - ✅
frontend/src/index.js - ✅
cli/src/main.py
# See which Python is being used
where python
python --version
# Check virtual environment
.venv\Scripts\python.exe --version# List installed packages
.venv\Scripts\pip.exe list
# Check specific package
.venv\Scripts\python.exe -c "import git; print('gitpython OK')"
.venv\Scripts\python.exe -c "import pydriller; print('pydriller OK')"# Check Node.js installation
where node
where npm
node --version
npm --version# Check PATH
echo %PATH%
# Check Python environment
.venv\Scripts\python.exe -c "import sys; print(sys.path)"If you're still having issues:
- Check the logs - Look for error messages in terminal output
- Verify versions - Ensure all tools meet minimum requirements
- Restart terminal - Sometimes PATH changes need a restart
- Check permissions - Make sure you have write access to the directory
- Python: 3.8 or higher
- Git: Any recent version
- Node.js: 16 or higher (for frontend development)
- OS: Windows 10+, macOS 10.15+, Ubuntu 18.04+
Once setup is complete:
- Run
python example.pyto test with sample data - Analyze your own repository:
python -m cli.src.main analyze /path/to/repo - Start the web interface:
python -m cli.src.main serve - Visit http://localhost:3001 to see your timeline!
Need more help? Check the main README or create an issue on GitHub.