feat: apollo-client-upload support #669
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
Resolves #553
β Type of change
π Description
The Nuxt Apollo module currently does not support file or
Blobuploads when usinguseMutation, forcing developers to rely on custom workarounds or abandon the module.This PR adds first-class support for file uploads by integrating apollo-upload-client and updating the Apollo client plugin to use an upload-enabled link by default.
Whatβs included
Adds file and
Blobupload support viaapollo-upload-clientUses the upload link as the default
httpLinkIntroduces a
useApolloUploadLinkoption:true(default): enables file uploadsfalse: falls back to the nativehttpLinkThis preserves backward compatibility while giving users full control.
Why this change is needed
Without this support, developers must:
This PR removes that friction and provides an out-of-the-box solution that aligns with common GraphQL use cases.
Version compatibility
This PR uses
apollo-upload-client@v18, which is compatible with the current dependency stack.I have also prepared a separate branch using
v19. It is available here:https://github.com/Anumide/nuxt-apollo/tree/feat/v19-apollo-client-upload
Supporting v19 requires dependency upgrades, which are already being addressed in related PRs:
Iβm happy to follow up with an updated PR once those changes land.