You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi friends! Tell me, please, faced with such a problem. I have a Nuxt project in which I am developing an admin panel for a website and I use vue-component-meta in it. If the project is deployed separately, then everything works great. But we decided that we needed to use a monorepository to poke components between the admin area and the site, so we chose turborepo for this. But after transferring the project to the monorepository, the meta for local components began to come empty, that is, the component is located, but all its props, slots, events are just empty arrays.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi friends! Tell me, please, faced with such a problem. I have a Nuxt project in which I am developing an admin panel for a website and I use vue-component-meta in it. If the project is deployed separately, then everything works great. But we decided that we needed to use a monorepository to poke components between the admin area and the site, so we chose turborepo for this. But after transferring the project to the monorepository, the meta for local components began to come empty, that is, the component is located, but all its props, slots, events are just empty arrays.
At the same time, everything works fine for Nuxt/Ui components. Does anyone know how to overcome this and where to look for the problem?
Beta Was this translation helpful? Give feedback.
All reactions