Andrew

Hi guys, any updates on this one?

maybe it's related to how you use the package? If you manually import it in your files that suppose to be working in production instance - ESLint will warn you...

Looks like it's something to do with `-` in your property name, you can workaround it by just using `title1` instead of `title-1`

Exactly, this is a must-have feature that can make working with zoned content way easier, especially with a multi-monitor scenario. I always wanted to be able to have a shortcut...

@danielroe how that GC can be triggered?

@danielroe @pi0 the issue was narrowed down to the memory leak from node 18.12 -> 18.13 to be the use of useLazyFetch with an external source. This seems to be...

@danielroe is this still an issue with Node 18.15.0?

@dakt prefixing is not always desired behavior, right now there are a lot of cases where overwriting is a more desirable behavior and you can easily implement a "prefixed" mode...

I tried ``` export default defineNuxtConfig({ sourcemap: { server: true, client: false } }) ``` but still get warnings  What is even more interesting is that it doesn't disappear...

We have this issue as well, memory usage is growing exponentially when the feature is enabled ``` experimental: { clientFallback: true } ``` ``` .... ```