fix(deps): update dependency @vercel/edge-config to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vercel/edge-config (source)	^0.4.1 -> ^1.0.0

---

Release Notes

vercel/storage (@​vercel/edge-config)

v1.1.0

Compare Source

Minor Changes

• 5fb6969: Make @opentelemetry/api optional and expose a setTracerProvider function

v1.0.2

Compare Source

Patch Changes

• 78d5814: prevents having too many open connections

v1.0.1

Compare Source

Patch Changes

• 4e7e216: mark @​opentelemetry/api as optional peer dependency

v1.0.0

Compare Source

Major Changes

• fcdc55e: - BREAKING CHANGE Return values are now read-only to improve in-memory caching

  It used to be possible to change the returned value as shown in this example:

  import { get } from '@​vercel/edge-config';
  const countries = await get('allowedCountryCodes');
  countries.DE = true; // Will now cause TypeScript to error

  Moving forward, modifications like the above will cause a type error.

  If there is a need to modify the value, then the clone function can be used to clone the data and make it modifiable.

  import { get, clone } from '@​vercel/edge-config';
  
  const myArray = await get('listOfAllowedIPs');
  const myArrayClone = clone(myArray); // Clones the data to make it modifiable
  myArrayClone.push('127.0.0.1'); // The `push` operation will work now

  • BREAKING CHANGE SDK now throws underlying errors

    Previous versions of the @vercel/edge-config package would catch most errors thrown by native functions and throw a generic network error instead - even if the underlying issue wasn't a network error. The new version will throw the original errors.

    Note applications which rely on the @vercel/edge-config: Unexpected error and @vercel/edge-config: Network error errors must adapt to the new implementation by ensuring other types of errors are handled as well.

  • The SDK now uses stale-while-revalidate semantics during development

    When @vercel/edge-config is used during development, with NODE_ENV being set to development, any read operation will fetch the entire Edge Config once and keep it in-memory to quickly resolve all other read operations for other keys, without waiting for the network. Subsequent reads will update the in-memory data in the background.

    This behaviour can be disabled by setting the environment variable EDGE_CONFIG_DISABLE_DEVELOPMENT_SWR to 1, or by using the disableDevelopmentCache option on the createClient function.

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vercel/edge-config@1.1.0	environment, network	+2	1.31 MB	vercel-release-bot

🚮 Removed packages: npm/@vercel/edge-config@0.4.1

View full report↗︎