geldata / geldata/quickstart-nextjs

Unable to run gel commands

Open
#1 0 comments 3 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Whenever I try to run a `gel` command with `npx` (like `npx gel migration create`) I get the following error

```sh
Newer version of edgedb tool exists 7.2.0+c5b8c5e (current 6.1.2+1e45048)
edgedb error: error reading project config `.../gel.toml`
Caused by: TOML parse error at line 1, column 1
|
1 | [instance]
| ^
missing field `edgedb`
```

Addding the empty `[edgedb]` field to `gel.toml` config kinda fixes the problem

```toml
[instance]
server-version = "6.1"

[edgedb]

[hooks]
schema.update.after = "npx @gel/generate edgeql-js"
```

But outputs the following warnings in the console

```sh
Newer version of edgedb tool exists 7.2.0+c5b8c5e (current 6.1.2+1e45048)
[2025-04-04T05:34:38Z WARN edgedb::portable::config] Unknown config option `hooks`
[2025-04-04T05:34:38Z WARN edgedb::portable::config] Unknown config option `instance`
Created...
```

The whole thing looks like a bug in `gel` given what's stated in the docs -> https://docs.geldata.com/reference/using/projects#instance-table

> For versions of Gel prior to 6.0 use [edgedb] table instead of [instance].

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the gel.toml configuration shown in the issue and reproduce the failure with npx gel migration create. Compare the [instance], [edgedb], and [hooks] tables with the linked project documentation and check the resulting warnings. Done means the quickstart configuration runs without the missing-field error or unknown-option warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, node.js, typescript
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.