-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty meta data #67
Comments
@BlueBazze I was experiencing the same issue as you (empty meta) and just figured it out. For me, some components were working and some were not. I'm not too sure if there are breaking changes but I now override the For your heap memory issue, idk but have you tried to exclude components from other modules that you don't need their meta information? 'componentMeta': {
exclude: [
'@nuxt/content',
'@nuxt/ui-templates',
'@nuxt/ui',
'@nuxt/ui-pro',
'@nuxtjs/color-mode',
... |
I have a layer with shadcn-vue which is built on top of radix-vue. Radix uses some deep typed props, sometimes even includes HTMLElement. vue-component-meta then maps out all the types which causes some component meta's to be hundreds of MB. Noticed the exclude allowed for a function to filter instead of the string regex. The root of the issue is whenever the components meta data gets too big node has a problem writing the data to a file. |
It seems that all meta data for all my components are empty.
Haven't been able to find a solution for this.
Versions
components/test.global.vue
.nuxt/components-meta.mjs
When i try to log this line in my node_modules, it seems to return an empty array.
Tried defining the props in the different ways, but to no avail.
I've checked the checker, and the component is present in the tsconfig.
Tried manually installing the latest version of vue-component-meta - 2.0.19
Now it works, except for updateOutput.
It fails on https://github.com/nuxtlabs/nuxt-component-meta/blob/main/src/parser.ts#L115-L119
After the writeFile is called, memory usage goes up by about 2.5 GB then throws Javascript heap out of memory.
I am able to console log all the writeFile params, and they seem alright.
Tested on node
22.1.0
22.2.0
20.14.0
It works fine if i make it print
JSON.stringify(components["Test"])
Well..... It seems fair..
Had a feeling that it was generating a lot of text..
So i tried
Instead of writeFile.
After taking a look at the file, it is now 210 mb before going out of heap.
After updating the printing
There is a total of 2 GB of json files.
The text was updated successfully, but these errors were encountered: