[nuxt] Could not access `pt`. The only available runtime config keys on the client side are `public` and `app`

primefaces / primevue-nuxt-module

MIT License

70 stars 11 forks source link

[nuxt] Could not access `pt`. The only available runtime config keys on the client side are `public` and `app` #69

Closed Tarabass closed 1 month ago

Tarabass commented 1 month ago

After a clean installation I get the following warning in the console. In bigger projects it can even result in an error instead of a warning.

[nuxt] Could not access 'pt'. The only available runtime config keys on the client side are 'public' and 'app'. See 'https://nuxt.com/docs/guide/going-further/runtime-config' for more information.

https://stackblitz.com/edit/github-ydzyjt

npx nuxi init NuxtPrimeVueTest
npx nuxi@latest module add primevue

borsTiHD commented 1 month ago

I have the same problem. I am trying to update an project to the latest dependencies.

Among others nuxt: v3.12.1 and Primevue with @primevue/nuxt-module: v4.0.0-rc.1

petter-tchirkov commented 1 month ago

Same issue here, fresh installation

kambanwait commented 1 month ago

Same issue here, just replicated it with the latest PrimeVue 'RC' and Nuxt version. Also happens with PrimeVue3 latest and latest Nuxt 😭:

https://stackblitz.com/edit/nuxt-starter-vxuc17?file=app.vue

petter-tchirkov commented 1 month ago

can anyone tell the latest working version?

Ice-Hazymoon commented 1 month ago

same issue.

Tarabass commented 1 month ago

Discussion in Nuxt; https://github.com/nuxt/nuxt/discussions/27645

Tarabass commented 1 month ago

can anyone tell the latest working version?

Downgrade nuxt to 3.11.2 will suppress the logging. Due to changes within Nuxt this warning is getting logged now, while the problem may have existed for a longer time.

mertsincan commented 1 month ago

Fixed in core. Thanks a lot for your reports!