apollo

🐛 Describe the bug When using @vue/apollo-composable in a Nuxt 3 (Vite) environment with @apollo/client@4.0.12, the application crashes at runtime with the following error: Uncaught (in promise) SyntaxError: The requested module '/_nuxt/node_modules/@apollo/client/legacyEntryPoints/core/index.js' does not provide an export named 'ApolloError' This happens because @vue/apollo-composable imports ApolloError and isApolloError from: @apollo/client/core/index.js In Vite/Nuxt environments, this may resolve to legacyEntryPoints/core, which does not export ApolloError, leading to a runtime failure. 🔁 To Reproduce Create a minimal Nuxt 4 project (Vite-based) Install: @vue/apollo-composable@4.2.2 @apollo/client@4.0.12 Trigger an error in a query/mutation (so toApolloError is executed) Run nuxt dev Observe runtime crash due to missing ApolloError export ✅ Expected behavior ApolloError should be imported from a stable and officially supported entrypoint that guarantees its availability. The application should not crash during error handling. 📦 Versions vue: 3.x @vue/apollo-composable: 4.2.2 @apollo/client: 4.0.12 Nuxt: 4.x Bundler: Vite 🔍 Root cause In: packages/vue-apollo-composable/src/util/toApolloError.ts There is: import { ApolloError, isApolloError } from '@apollo/client/core/index.js' However, in Apollo Client v4, ApolloError is exported from: @apollo/client/errors Importing from the core entrypoint is unsafe in modern ESM + Vite environments because it may resolve to legacyEntryPoints, which does not export ApolloError. 💡 Proposed fix Replace: import { ApolloError, isApolloError } from '@apollo/client/core' With: import { ApolloError, isApolloError } from '@apollo/client/errors' This resolves the issue completely