* fix(db): eliminate concurrent-read "database is locked"; add node:sqlite backend (#238) WAL + busy_timeout were already enabled, so the issue's suggested fix was a no-op. The real causes, addressed here: - busy_timeout is now set first (before journal_mode) and lowered 120s -> 5s, so open-time pragmas wait out a lock instead of hanging for two minutes. - getCodeGraph no longer opens a second connection to the default project when a tool passes its own projectPath (the in-process lock amplifier). - The wasm fallback (no WAL) gets a bounded read-retry on SQLITE_BUSY. - New: node:sqlite backend, preferred over wasm, so installs whose native better-sqlite3 build fails land on a real-WAL backend instead of no-WAL wasm. - codegraph status / codegraph_status now report the effective journal mode, so a lock report is triageable (wal vs delete). - CLI hard-blocks Node < 20 to actually enforce the engines floor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * refactor(db)!: node:sqlite is the sole backend; drop better-sqlite3 + wasm Now that distribution will bundle a Node 24 runtime, node:sqlite (real SQLite with WAL + FTS5) is always available. Collapse the three-backend adapter to node:sqlite only and remove the machinery the other two needed: - Remove better-sqlite3 (optionalDependency) and node-sqlite3-wasm (dependency). - Remove WasmDatabaseAdapter, the named->positional param translation, the SQLITE_BUSY read-retry, the wasm fallback banner, the backend env override, and the native/node-sqlite/wasm selection chain. - createDatabase now opens node:sqlite directly, with a clear error pointing at the bundled release / Node 22.5+ when the module is absent. - NodeSqliteAdapter.close() is idempotent and pragma() supports { simple }, to match the better-sqlite3 behavior callers relied on. - status (CLI + MCP) reports the single node:sqlite backend; journal-mode diagnostics and the getCodeGraph single-connection fix are retained. - Tests repointed off better-sqlite3 onto node:sqlite. Net -1044 lines. Running from source now requires Node 22.5+. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(dist): self-contained bundle prototype (vendored Node + install channels) Phase 3 of the node:sqlite migration: ship a vendored Node runtime so CodeGraph runs with no system Node and no native build (node:sqlite is built in). - scripts/build-bundle.sh: build a per-platform archive (official Node + dist + prod deps + launcher). Same recipe per platform; pins Node v24.16.0. - install.sh: curl|sh installer (no Node required) — detects os/arch, pulls the archive from Releases, symlinks onto PATH; re-run to upgrade, --uninstall to remove. The VPS/SSH path. - scripts/npm-shim.js: thin launcher for the npm channel — resolves the per-platform optionalDependency bundle and execs it, so `npm i -g` keeps working and the real work runs on the bundled Node regardless of the user's. - BUNDLING.md: distribution design + release-pipeline TODO (CI matrix, platform packages, code signing, brew, retiring the Node-version gate). Validated end-to-end: darwin-arm64 and linux-x64 bundles both run init + index + status (Backend: node:sqlite, Journal: wal) + FTS query with NO system Node — linux-x64 verified in a clean ubuntu:24.04 amd64 container. Release archives are gitignored; CI will produce and upload them. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(dist): add Windows PowerShell installer (install.ps1) The `irm … | iex` one-liner for Windows, mirroring install.sh: detect arch, pull the matching bundle from Releases, extract to %LOCALAPPDATA%\codegraph, add it to user PATH. Re-run to upgrade. (Windows bundle production in build-bundle.sh is still TODO.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(dist): release workflow + npm packaging; README/CHANGELOG for bundled distro - .github/workflows/release.yml: manually-triggered (workflow_dispatch) release matrix. Builds a self-contained bundle per platform on its own runner (darwin-arm64/x64, linux-x64/arm64), publishes a GitHub Release with all archives, and publishes the npm thin-installer (shim + per-platform packages). Windows targets are TODO (build-bundle.sh is unix-only). - scripts/pack-npm.sh: assemble the npm packages from built bundles — per-platform packages tagged os/cpu + the main shim package with them as optionalDependencies (esbuild pattern). Proven locally: npm-install the tarballs, run via the shim, resolves the bundle and runs on the bundled Node 24 (node:sqlite / WAL). - README: install section now leads with the no-Node one-liners (curl|sh, irm|iex) then npm/npx; "bundled · none required" badge. - CHANGELOG: standout headline for the self-contained release, plus Added/Changed/ Removed for the install channels, node:sqlite backend, and dropped deps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(dist): Windows bundles + single-trigger release workflow - build-bundle.sh: add win32-x64 / win32-arm64 targets — download Node's Windows zip, bundle node.exe + a .cmd launcher, output a .zip. Verified structurally (PE32+ node.exe, CRLF .cmd, portable node_modules). Since there are no native addons, any target builds on any OS, so the whole matrix builds on one runner. - pack-npm.sh: handle .zip bundles and win32 packages (os: win32, node.exe). - release.yml: simplified to your spec — manual trigger reads the version from package.json, builds all platform bundles, creates the GitHub Release with notes pulled from CHANGELOG.md, and publishes the npm shim + platform packages. - BUNDLING.md: Windows + build-anywhere notes; release pipeline documented. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
60 lines
2.6 KiB
PowerShell
60 lines
2.6 KiB
PowerShell
# CodeGraph standalone installer for Windows (PowerShell).
|
|
#
|
|
# Downloads a self-contained bundle (a vendored Node runtime + the app) from
|
|
# GitHub Releases. No Node.js, no build tools required.
|
|
#
|
|
# irm https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.ps1 | iex
|
|
#
|
|
# Re-run to upgrade. To uninstall: remove $env:LOCALAPPDATA\codegraph and drop
|
|
# its \current\bin entry from your user PATH.
|
|
#
|
|
# Environment:
|
|
# CODEGRAPH_VERSION release tag to install (default: latest)
|
|
# CODEGRAPH_INSTALL_DIR install location (default: %LOCALAPPDATA%\codegraph)
|
|
|
|
$ErrorActionPreference = 'Stop'
|
|
$repo = 'colbymchenry/codegraph'
|
|
$installDir = if ($env:CODEGRAPH_INSTALL_DIR) { $env:CODEGRAPH_INSTALL_DIR } else { Join-Path $env:LOCALAPPDATA 'codegraph' }
|
|
|
|
# 1. Detect architecture -> target matching the release archives.
|
|
$arch = if ([System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture -eq 'Arm64') { 'arm64' } else { 'x64' }
|
|
$target = "win32-$arch"
|
|
|
|
# 2. Resolve the version (latest release unless pinned).
|
|
$version = $env:CODEGRAPH_VERSION
|
|
if (-not $version) {
|
|
$version = (Invoke-RestMethod "https://api.github.com/repos/$repo/releases/latest").tag_name
|
|
}
|
|
if (-not $version) { throw "codegraph: could not resolve latest version; set CODEGRAPH_VERSION." }
|
|
|
|
# 3. Download + extract the bundle into a stable 'current' dir (overwritten on upgrade).
|
|
$url = "https://github.com/$repo/releases/download/$version/codegraph-$target.zip"
|
|
Write-Host "Installing CodeGraph $version ($target)..."
|
|
$tmp = Join-Path $env:TEMP ("cg-" + [guid]::NewGuid().ToString())
|
|
New-Item -ItemType Directory -Force -Path $tmp | Out-Null
|
|
$zip = Join-Path $tmp 'cg.zip'
|
|
Invoke-WebRequest -Uri $url -OutFile $zip
|
|
|
|
$dest = Join-Path $installDir 'current'
|
|
if (Test-Path $dest) { Remove-Item -Recurse -Force $dest }
|
|
New-Item -ItemType Directory -Force -Path $dest | Out-Null
|
|
Expand-Archive -Path $zip -DestinationPath $dest -Force
|
|
# Archives contain a top-level codegraph-<target>\ dir; flatten it.
|
|
$inner = Join-Path $dest "codegraph-$target"
|
|
if (Test-Path $inner) {
|
|
Get-ChildItem -Force $inner | Move-Item -Destination $dest -Force
|
|
Remove-Item -Recurse -Force $inner
|
|
}
|
|
Remove-Item -Recurse -Force $tmp
|
|
|
|
# 4. Put the launcher dir on the user's PATH.
|
|
$binDir = Join-Path $dest 'bin'
|
|
$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
|
|
if (($userPath -split ';') -notcontains $binDir) {
|
|
[Environment]::SetEnvironmentVariable('Path', "$binDir;$userPath", 'User')
|
|
Write-Host "Added $binDir to your PATH (restart your terminal to pick it up)."
|
|
}
|
|
|
|
Write-Host "Installed to $dest"
|
|
Write-Host "Run: codegraph --help"
|