Joaquín Sánchez
Joaquín Sánchez
@serkodev You need to change the node `max_old_space_size` here https://github.com/vueuse/vueuse/blob/main/netlify.toml#L6 Just try with 8192 (the free tier is limited to 6GB), iirc Anthony doesn't have any restriction at Netlifly
@serkodev don't waste your time, looks like it is a problem with Vue version, check: - https://github.com/vuejs/vitepress/issues/4242 - https://github.com/shikijs/shiki/issues/796 If we can run the build at Netlify with 16GB it...
@serkodev Maybe you can try with VP 2.0.2.alpha (using Vite 6) in a new local branch from this one (or even using a new clean clone of the branch, no...
we can also try updating the dependency to latest version 2.3.2: https://github.com/vueuse/vueuse/blob/main/pnpm-workspace.yaml#L12
Thx @brc-dd : > You can try enabling the [fs cache thing](https://shiki.style/packages/vitepress#file-system-cache) that twoslash added (it might not work though 🫠). Twoslash is rebuilding whole ts graph for each file...
can you try updating shikijs and shikijs vitepress to latest versions?
can you try with VP ^1.6.3 instead 2 alpha?
You can add `upath` and `@vuetify/loader-shared` as dev dependencies, then, add this module to your modules folder https://github.com/vuetifyjs/create/pull/61/files#diff-4b4c4cd18da70e601d2655333385b40296a6604e786e298bd5e1d1a8c398c594R1 Remove `vite-plugin-vuetify` from your nuxt config file and add the vuetify plugin...
No, you will use it in the new module but only to auto import vuetify components: you can remove that inlined module, the new module will register it properly disabling...
On my latpop also reproducible (i7 12700H): - `v0.58.9`: `[loadConfig]: 889.937ms` - `v0.60.2`: `[loadConfig]: 1.620s`