neondatabase / neondatabase/serverless
TypeError: fetch failed] { cause: [Error: AggregateError] }
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 548
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
const sql = neon(process.env.POSTGRES_URL_NON_POOLING);
return await sql(query, params);
Expected result
Return rows
Actual result
Error
Environment
Vercel Edge Runtime
Logs, links
Work with Kysely and Pool, but this does not work:
const sql = neon(process.env.POSTGRES_URL_NON_POOLING);
return await sql(query, params);
[NeonDbError: Error connecting to database: fetch failed] {
name: 'NeonDbError',
severity: undefined,
code: undefined,
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: undefined,
line: undefined,
routine: undefined,
sourceError: [TypeError: fetch failed] { cause: [Error: AggregateError] }
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction snippet in the issue under the Vercel Edge Runtime, using Neon with Kysely and Pool, and investigate the reported fetch failed AggregateError. Done means the query returns rows instead of producing the NeonDbError shown in the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100