Jerry Kusenberger

Results 7 comments of Jerry Kusenberger

Auto-imports commit breaks compilation in large project

I started experiencing this issue when upgrading from nuxt bridge 3.0.0-27982868.cf7ca7b to 3.0.0-27998567.a12a710. Is there a workaround?

_nuxt/empty.js was blocked with vite:true and ssr:false

I am also experiencing this. The workaround from @AndreyYolkin did not work for me.

_nuxt/empty.js was blocked with vite:true and ssr:false

Yes I have nitro enabled. In my bridge options I set vite: true. Everything works if I set vite: false

_nuxt/empty.js was blocked with vite:true and ssr:false

I just created an empty repo with just nuxt and nuxt bridge installed. This is all that is in the nuxt config. If I set SSR to true the problem...

_nuxt/empty.js was blocked with vite:true and ssr:false

thanks @AndreyYolkin I'm one step closer. Now experiencing the same ENOENT issue.

Building Nitro Server - Out Of Memory

+1 same issue for me. Upgrade from nuxt 2 to bridge. I can build locally but am unable to build using github actions

Building Nitro Server - Out Of Memory

As a workaround, I disabled nitro which allows me to stay on nuxt-edge and bridge. export default defineNuxtConfig({ bridge: { nitro: false, }, .....