nuxt app instance unavailable with Apollo Graphql

[Luferov]

Environment

---

• Operating System: Darwin
• Node Version: v16.15.1
• Nuxt Version: 2.16.0-27616340.013f051b
• Package Manager: [email protected]
• Builder: webpack
• User Config: ssr, app, alias, target, publicRuntimeConfig, head, modules, apollo, typescript, css, plugins, vuetify, build, serverHandlers, devServerHandlers, bridge, buildModules
• Runtime Modules: @nuxtjs/[email protected], @nuxtjs/[email protected], @nuxtjs/[email protected], @nuxtjs/[email protected], @pinia/[email protected]
• Build Modules: (), @nuxt/[email protected]

---

Reproduction

https://github.com/Luferov/nuxt-graphql-bug

git clone [email protected]:Luferov/nuxt-graphql-bug.git
cd nuxt-graphql-bug
yarn

OK, its work! But

rm -r node_modules && rm -r .nuxt && yarn

It is not work.

Describe the bug

I created yarn.lock from my project and project is wok. But if delete yarn.lock and run command yarn, Nuxt will update up nuxt 3-rc and project is not working.

Additional context

No response

Logs

[nuxt] [request error] nuxt app instance unavailable
  at useNuxtApp (./.nuxt/dist/server/server.js:15661:13)  
  at useRuntimeConfig (./.nuxt/dist/server/server.js:16127:78)  
  at ./.nuxt/dist/server/server.js:66176:68  
  at module.exports../.nuxt/apollo-module.js.__webpack_exports__.default (./.nuxt/dist/server/server.js:404:25)  
  at createApp (./.nuxt/dist/server/server.js:1463:93)  
  at async module.exports../.nuxt/server.js.__webpack_exports__.default (./.nuxt/dist/server/server.js:3687:7)  
  at async Object.renderToString (./node_modules/vue-bundle-renderer/dist/index.mjs:264:19)  
  at async ./.nuxt/dev/index.mjs:499:20  
  at async ./node_modules/h3/dist/index.mjs:492:19  
  at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:438:7)

[Luferov]

May it depend with #436

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v2-bridge
👉 https://codesandbox.io/p/github/nuxt/starter/v2-bridge-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[github-actions]

This issue was closed because it was open for 7 days without a reproduction.