Mads Comments - Answer Overflow

bunx vue-tsc --noEmit --listFiles | grep -E '\.vue$|\.ts$|\.tsx$' | xargs -n 1 stat --format="%s %n" | bunx webtreemap-cli


<--- Last few GCs --->

[9818:0x150008000]    59607 ms: Mark-Compact 4039.3 (4131.2) -> 4023.8 (4131.7) MB, 618.58 / 0.00 ms  (average mu = 0.118, current mu = 0.009) allocation failure; scavenge might not succeed
[9818:0x150008000]    60208 ms: Mark-Compact 4039.8 (4131.7) -> 4024.4 (4132.2) MB, 595.33 / 0.00 ms  (average mu = 0.067, current mu = 0.009) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x1010a50ac node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/Users/madshjorth/.nvm/versions/node/v20.12.0/bin/node]

bunx vue-tsc --noEmit --listFiles | grep -E '\.vue$|\.ts$|\.tsx$' | xargs -n 1 stat --format="%s %n" | bunx webtreemap-cli


<--- Last few GCs --->

[9818:0x150008000]    59607 ms: Mark-Compact 4039.3 (4131.2) -> 4023.8 (4131.7) MB, 618.58 / 0.00 ms  (average mu = 0.118, current mu = 0.009) allocation failure; scavenge might not succeed
[9818:0x150008000]    60208 ms: Mark-Compact 4039.8 (4131.7) -> 4024.4 (4132.2) MB, 595.33 / 0.00 ms  (average mu = 0.067, current mu = 0.009) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x1010a50ac node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/Users/madshjorth/.nvm/versions/node/v20.12.0/bin/node]

14 replies

NNuxt

•Created by Tom on 1/20/2025 in #❓・help

App.vue overwritten by layer after adding @nuxt/content@3

That was quick! Love it. ♥️

29 replies

NNuxt

•Created by Tom on 1/20/2025 in #❓・help

App.vue overwritten by layer after adding @nuxt/content@3

Sorry it’s Nuxt/Content v3 that’s causing this like op suggested. Downgrading did not help

29 replies

NNuxt

•Created by Tom on 1/20/2025 in #❓・help

App.vue overwritten by layer after adding @nuxt/content@3

Basically Nuxt can’t see current layer

29 replies

NNuxt

•Created by Tom on 1/20/2025 in #❓・help

App.vue overwritten by layer after adding @nuxt/content@3

@Tom there is definitely a bug in layers after upgrading from from Nuxt 3.14.1592 to 3.15.2 I would suggest to downgrade until it is fixed. @danielroe when using Layers And having this app.config.ts in base layer // base layer export default defineAppConfig({ myLayer: { name: 'base' as 'base' | 'kassebil' | 'maxgarage' | 'hellocar', }, }) When I deploy the Kassebil layer it will still show myLayer.name === base if the component comes from this layer. Even with this app.config.ts in kassebil layer // base layer export default defineAppConfig({ myLayer: { name: 'kassebil' as 'base' | 'kassebil' | 'maxgarage' | 'hellocar', }, }) I will try to make a minimal repro soon

29 replies

NNuxt

•Created by Jonas on 9/28/2024 in #❓・help

Couldn't resolve component "default" at "/"

18 replies

NNuxt

•Created by Bobbo on 10/11/2024 in #❓・help

Upgrading from 3.5.0 to 3.13.2 is breaking build

useId is a Vue 3.5 thing. Try installing the latest version of Vue

14 replies

DTDrizzle Team

•Created by BEEIRL on 8/23/2024 in #help

PlanetScale drizzle-kit push: Cannot drop index: needed in a foreign key constraint

I experience the same.

3 replies

DTDrizzle Team

•Created by theo (t3.gg) on 9/3/2024 in #help

Consistent issues with `drizzle-kit push` on Turso

I appreciate it, thanks Andrew. Let me know if there is anything I can do.

24 replies

DTDrizzle Team

•Created by theo (t3.gg) on 9/3/2024 in #help

Consistent issues with `drizzle-kit push` on Turso

Sorry for hijacking. Any chance we can get Push to work on Planetscale working again @Andrew Sherman 🙂 https://github.com/drizzle-team/drizzle-orm/issues/2599 I can provide a Planetscale database if you need it for testing.

24 replies

DTDrizzle Team

•Created by Mads on 8/31/2024 in #help

notNull and Unique

https://github.com/drizzle-team/drizzle-orm/issues/2599 This seems to be the issue.

7 replies

DTDrizzle Team

•Created by Mads on 8/31/2024 in #help

notNull and Unique

Well that added the unique constraint. But it still complaints about I’m about to add a new unique constraint.

7 replies

DTDrizzle Team

•Created by Mads on 8/31/2024 in #help

notNull and Unique

Moving unique() to the end fixed it: name: varchar('name', { length: 255 }).notNull().unique(),

7 replies

DTDrizzle Team

•Created by Mads on 8/31/2024 in #help

notNull and Unique

7 replies

NNuxt

•Created by Pawieplays on 8/26/2024 in #❓・help

Metadata for Route

Or maybe be wrong. You want to do a navigation and pass some data along, without setting a query? It seems like the wrong approach. I would look into using setting a useState or maybe definePageMeta like so. definePageMeta({ pageType: 'Checkout', })

3 replies

NNuxt

•Created by Pawieplays on 8/26/2024 in #❓・help

Metadata for Route

You still can using definePageMeta.

3 replies

Gaming

Programming