# How to Update gods-eye-view to the Latest Version: Pinokio and Terminal Methods Explained

> Easily update gods-eye-view to the latest version using Pinokio or the terminal. Learn simple commands to pull updates and reinstall dependencies for a seamless experience.

- Repository: [Bilawal Sidhu/gods-eye-view](https://github.com/bilawalsidhu/gods-eye-view)
- Tags: how-to-guide
- Published: 2026-09-05

---

**Run `node scripts/pinokio-update.mjs` in the repository root, or click Update in the Pinokio launcher, to pull the latest commits via git and reinstall exact dependencies with `npm ci`.**

**gods-eye-view** (bilawalsidhu/gods-eye-view) is a Node.js application distributed through both the **Pinokio** one-click launcher and traditional git clones. Keeping the tool current ensures access to the latest satellite imagery features and stability fixes. This guide covers both update paths in detail, with direct reference to the source scripts that power the process.

## Pinokio One-Click Update Method

The simplest way to update gods-eye-view is through the Pinokio UI—no terminal required.

### Prerequisites

- Pinokio version 8.2 or later (earlier versions had launcher installation issues noted in the README)

### Update Steps

1. Open **God's Eye View** in your Pinokio library
2. Click **Install** → **Start**
3. If the app is already running, click the **Update** button that appears when a newer release exists
4. Wait for the progress bar to complete—Pinokio automatically executes `scripts/pinokio-update.mjs`
5. Relaunch the application

Behind the scenes, Pinokio runs the update script which performs `git pull --ff-only` and refreshes all `node_modules` to match [`package-lock.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package-lock.json).

## Terminal-Based Update Method

For developers or users who cloned the repository manually, use the command line for full control.

### Using the Built-In Update Script

The repository includes `scripts/pinokio-update.mjs` for streamlined updates:

```bash

# Navigate to your clone

cd path/to/gods-eye-view

# Execute the bundled updater

node scripts/pinokio-update.mjs

```

This script internally runs:

```javascript
runChecked('git', ['pull', '--ff-only']);
installPinokioDependencies();

```

The `installPinokioDependencies()` function (defined in `scripts/pinokio-install.mjs`) executes `npm ci` to guarantee exact dependency versions.

### Manual Git and NPM Update

For complete visibility into each step:

```bash

# 1. Enter the repository

cd ~/projects/gods-eye-view

# 2. Fetch and fast-forward to latest commits

git fetch --prune
git pull --ff-only

# 3. Reinstall exact dependency tree

npm ci

# 4. Verify environment health

npm run doctor

# 5. Start fresh (clears Vite caches)

npm run dev

```

Or use the convenience script that clears caches automatically:

```bash
./scripts/dev-fresh.sh

```

## What the Update Script Actually Does

Understanding `scripts/pinokio-update.mjs` helps troubleshoot edge cases.

| Step | Command | Purpose |
|------|---------|---------|
| Git sync | `git pull --ff-only` | Fetches new commits; fails safely if local changes would conflict |
| Dependency sync | `npm ci` | Wipes `node_modules` and reinstalls exact versions from [`package-lock.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package-lock.json) |
| Health check | (optional) `npm run doctor` | Validates Node version, API keys, and environment |

The `--ff-only` flag is critical: it prevents merge commits on a clean installation, ensuring the working directory stays in a known-good state.

## Verifying Your Update

After any update method, confirm success:

1. Check the version displayed on the splash screen against [`CHANGELOG.md`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/CHANGELOG.md)
2. Run the doctor command to validate the environment:

```bash
npm run doctor

```

3. Review the latest commit: `git log --oneline -1`

## Troubleshooting Common Update Issues

| Symptom | Cause | Solution |
|---------|-------|----------|
| "Merge conflict" error | Local modifications present | Stash changes with `git stash` before updating |
| Dependency errors | Corrupted `node_modules` | Delete `node_modules` and [`package-lock.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package-lock.json), then run `npm ci` |
| Pinokio "Update" button missing | Running Pinokio < 8.2 | Update Pinokio itself from pinokio.com |
| Version mismatch after update | Cached Vite build | Run [`./scripts/dev-fresh.sh`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/./scripts/dev-fresh.sh) to clear caches |

## Summary

- **Pinokio users**: Click Update in the launcher—Pinokio runs `scripts/pinokio-update.mjs` automatically
- **Terminal users**: Run `node scripts/pinokio-update.mjs` or manually execute `git pull --ff-only && npm ci`
- **Always verify**: Check [`CHANGELOG.md`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/CHANGELOG.md) and run `npm run doctor` after updating
- **Cache clearing**: Use [`scripts/dev-fresh.sh`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/scripts/dev-fresh.sh) if the UI behaves unexpectedly post-update

## Frequently Asked Questions

### What is the fastest way to update gods-eye-view?

The Pinokio one-click update is fastest: open the app in Pinokio and click the **Update** button. This single action triggers `scripts/pinokio-update.mjs`, which pulls the latest code and reinstalls dependencies without any terminal interaction.

### Can I update gods-eye-view without reinstalling dependencies?

No—this is not recommended. The [`package.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package.json) and [`package-lock.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package-lock.json) files in the repository define exact dependency versions required for compatibility. Skipping `npm ci` (called automatically by the update scripts) risks runtime errors from mismatched package versions.

### Why does the update use `git pull --ff-only` instead of a regular pull?

The `--ff-only` flag ensures updates only succeed when your local branch can fast-forward to the remote. This prevents merge conflicts on clean installations and protects users from accidentally creating complex git histories. If you see a fast-forward error, you likely have local changes that need handling first.

### What should I do if the Pinokio Update button doesn't appear?

First, confirm your Pinokio version is 8.2 or later—earlier versions had launcher bugs that prevented proper update detection. If updated and the button still doesn't appear, use the terminal method: `node scripts/pinokio-update.mjs` from the repository directory.