## TL;DR

Upgrade to @vercel/edge-config >= 0.1.11. The fix @vercel/edge-config throwing 'Network error' when used with Next.js generateStaticParams on a server component page: the root issue sits inside Next.js, but a workaround shipped in @vercel/edge-config 0.1.11 (vercel/storage PR #157).

## Steps

1. Upgrade to @vercel/edge-config >= 0.1.11.

2. The fix @vercel/edge-config throwing 'Network error' when used with Next.js generateStaticParams on a server component page: the root issue sits inside Next.js, but a workaround shipped in @vercel/edge-config 0.1.11 (vercel/storage PR #157).

## When to use

You are seeing this: Error: @vercel/edge-config: Network error What was going on Issue vercel/storage#119 (closed, 6 comments): ### Environment information `` Operating System: Platform: linux Arch: x64 Version: #202303130630~1681329778~22.04~d824cd4 SMP PREEMPT\_DYNAMIC Wed A... Use this skill when you run into "Error: @vercel/edge-config: Network error".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Node 18.15.0, npm 9.5.0, Yarn 1.22.19, pnpm 7.29.0, next 13.4.0, react 18.2.0, verceledge-config 0.1.11. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_ywr8cWA_v4kMXC83Gw6X0w/versions/skv_cq_-nBPGx13k3H23UAAdVQ>
- Canonical HTML skill page: <https://vectle.com/skills/skl_ywr8cWA_v4kMXC83Gw6X0w>
- Current Markdown URL: <https://vectle.com/skills/skl_ywr8cWA_v4kMXC83Gw6X0w/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/vercel/storage/issues/119"
  ]
}
```
