chore(deps): bump nuxt-api-party from 3.4.2 to 4.0.0

[dependabot]

Bumps nuxt-api-party from 3.4.2 to 4.0.0.

Release notes

Sourced from nuxt-api-party's releases.

v4.0.0

Migration

Nuxt 4 Is Required

The module no longer supports Nuxt 3.

openapi-typescript v7 Is Required

The peer dependency used to accept ^5 || ^6 || ^7 and now accepts ^7 alone. Upgrade the package alongside the module and regenerate your schema types.

The experimental Namespace Is Gone

Its four flags moved out and two of them changed their default:

Before	Now	Default
experimental.enablePrefixedProxy: true	server.proxyMode: 'passthrough'	Unchanged
experimental.disableClientPayloadCache: true	payloadCache: false	Unchanged
experimental.enableAutoKeyInjection: true	Removed	Always on
experimental.enableSchemaFileWatcher	Removed	Always on in dev

Every useMyApiData call now gets its own async data state, keyed by its position in your source, the way Nuxt keys useFetch and useAsyncData – with no switch either way, as Nuxt has none. Two components asking for the same resource therefore no longer share a data ref, and no longer collide when their transform, pick or default options differ. They do still share the underlying request. Pass the same explicit key to put two call sites back on one instance.

The schema file watcher no longer has a switch. Nuxt's own builder watcher cannot stand in for it – it covers each layer's app and server directories only, and a path registered through nuxt.options.watch restarts the dev server rather than regenerating the types.

refresh() Sends the Request Again

The request cache sits below Nuxt's async data, so Nuxt could not reach into it: refresh(), clear() and a key change driven by a reactive option were answered with the response already cached for that request. Each of them now sends a new request. Expect more traffic where a page refreshes on an interval, and reach for getCachedData to decide when a call site may keep what it has.

cache Only Means the Browser Cache Now

cache used to accept a boolean alongside the RequestInit.cache values, and the boolean drove the payload cache. Payload caching now has its own option:

 const { data } = await useMyApiData('posts', {
-  cache: false,
+  payloadCache: false
 })

cache: true and cache: false are compile errors, so they surface on upgrade. One change is silent, though: a string value used to turn payload caching off as a side effect. cache: 'no-store' now only sets the browser cache mode, and the payload cache stays on unless you add payloadCache: false.

The Wrapped Proxy Reports 502 for an Unreachable API

An API that cannot be reached used to yield 503 Service Unavailable from the default proxy and 502 Bad Gateway from the passthrough one. Both report 502 now.

The Passthrough Proxy No Longer Forwards authorization

With server.proxyMode set to 'passthrough', a browser request's authorization header used to travel on to your API. It no longer does: the header carries the caller's credentials for your app, not your app's credentials for the upstream service.

... (truncated)

Commits

• d7ff357 chore: release v4.0.0
• 0cd50a3 chore: drop the release-age pins that have aged out
• c93bd3b docs: describe how an endpoint merges into the global openAPITS options
• dc97420 test(openapi): pin the option merge, multiple endpoints and the indentation
• 15b55f1 refactor(openapi): build each module declaration in one pass
• f887a3d fix(openapi): substitute every occurrence of a path parameter
• 38385a3 docs: rebuild the brand palette in OKLCH around the logo blue
• 7d5ae80 refactor(openapi): source the shared type helpers from apiful
• c4c908a chore: drop the duplicate env entry from the ignore file
• f741c82 refactor: scope every log line to the module that writes it
• Additional commits viewable in compare view