injection "Symbol(route location)" not found

[n4an]

Environment

nuxt 3
ubuntu

Reproduction

If i put project in one dir it work, if move to other not work. Always something not work.

Describe the bug

[log warn] injection "Symbol(route location)" not found. Proxy at <Anonymous>
at <App>
at <NuxtRoot>

logger.plugin.ts:4 [log error] TypeError: Cannot read properties of undefined (reading 'meta')
    at ReactiveEffect.fn (layout.mjs?v=57006e23:43:62)
    at ReactiveEffect.run (chunk-Q5TZPECP.js?v=57006e23:388:19)
    at get value [as value] (chunk-Q5TZPECP.js?v=57006e23:1215:35)
    at Proxy.<anonymous> (layout.mjs?v=57006e23:56:32)
    at renderComponentRoot (chunk-Q5TZPECP.js?v=57006e23:1941:39)
    at hydrateSubTree (chunk-Q5TZPECP.js?v=57006e23:5591:32)
    at ReactiveEffect.componentUpdateFn [as fn] (chunk-Q5TZPECP.js?v=57006e23:5608:13)
    at ReactiveEffect.run (chunk-Q5TZPECP.js?v=57006e23:388:19)
    at instance.update (chunk-Q5TZPECP.js?v=57006e23:5710:52)
    at setupRenderEffect (chunk-Q5TZPECP.js?v=57006e23:5718:5) Proxy render function






-----


at Array.join ()
at warn2 (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:1263:18)
at handleMismatch (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:5081:5)
at onMismatch (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:4878:30)
at hydrateNode (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:4909:22)
at hydrateSubTree (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:5598:13)
at ReactiveEffect.componentUpdateFn [as fn] (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:5608:13)
at ReactiveEffect.run (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:388:19)
at instance.update (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:5710:52)
at setupRenderEffect (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:5718:5)

Additional context

No response

Logs

No response

[danielroe]

Try removing your .nuxt folder.

[DamianGlowala]

I can confirm I am getting the exact same message on the latest Nuxt edge. It occurs 'randomly' though; sometimes the app won't start, sometimes it will.

[danielroe]

@DamianGlowala Would you give some info about your project, and ideally a reproduction? Do you have an exact version number? Are you using the pages/ integration?

[DamianGlowala]

This started happening after an upgrade from 3.0.0-rc.13-27778536.1d795f0 to 3.0.0-rc.13-27779883.2284525. And yes, I do use pages in the project.

---

• Operating System: Windows_NT
• Node Version: v16.13.0
• Nuxt Version: 3.0.0-rc.13-27779883.2284525
• Nitro Version: 0.6.1-27779851.28e2880
• Package Manager: npm@8.13.2
• Builder: vite
• User Config: app, ssr, modules, css, typescript, alias, build, runtimeConfig, vue, vite, proxy, headlessui
• Runtime Modules: @nuxtjs/tailwindcss@6.1.1, floating-vue/nuxt, @pinia/nuxt@0.4.3, @vueuse/nuxt@9.4.0, unplugin-icons/nuxt, @formkit/nuxt@1.0.0-beta.11-c95e605, nuxt-proxy@0.3.0, @nuxtjs/critters@0.3.3, nuxt-icon@0.1.7, nuxt-headlessui@1.0.1
• Build Modules: -

---

[n4an]

Also it say that some page doesn't exists thousands time in console log when put mouse on it, but page exists for years on it place :)

[n4an]

some times it say that inject can be used only in setup

[n4an]

with the i18n module was the same i think, because when i copy my project to fresh nuxt installation it work

[n4an]

and that shit with at Array.join () in at warn2 (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-Q5TZPECP.js?v=57006e23:1263:18)

[danielroe]

A reproduction please @n4an 🙏

[n4an]

A reproduction please @n4an pray

@danielroe I've had enough.
I do them for nothing.
Try to use yourself what you do.

[DamianGlowala]

First of all, please mind your language and be respectful towards the other members of the community.

Second of all, an error message is not a reproduction. As much as everyone understands the frustration, it might be naturally difficult to determine the cause of the issue without being able to reproduce such a behavior. See https://v3.nuxtjs.org/community/reporting-bugs#create-a-minimal-reproduction for more information. I will try to prepare a reproduction myself in the evening.

On a side note, please do not post multiple consecutive comments (as the ones above) when you can use an 'Edit' option and keep only one. Each one of them triggers an email notification to everyone involved in this thread.

[danielroe]

Apologies everyone for that. And thank you @DamianGlowala for an exemplary response. ❤️ We will track this issue in nuxt/nuxt#15288 and do our best to resolve. 😊