lutejka

@visualfanatic After Updating to `[email protected]` I'm facing the same issue as described in #57 though

I created #17 to handle this

I cant remember it was either 0.10.* or 0.11*. I also just tested it with 0.12.0 and it still happens 

When testing a other side I also got these errors a bunch ``` ERROR Failed to set cookies Protocol error (Network.deleteCookies): Target closed Unlighthouse 10:38:48 PM at CallbackRegistry.clear (/Users/lukas.matejka/.npm/_npx/944abecbf21dfffb/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:69:36) at...

The documentation states neither that `await` is needed nor that `await` is not needed. But this note at least seems to imply that it is optional. https://github.com/nuxt/nuxt/blob/1f09e69335426c221617994aaeec556671c23aa4/docs/3.api/2.composables/use-async-data.md?plain=1#L102-L104

Yes, exactly. I tried fetching the mounts when the RPC is called. But its still missing the mount I added via the nitro plugin 🤔 ```ts //... async getStorageMounts() {...

The 'asset' mount is available either... I took a look at nitro, and it seems like it create to different storage instances https://github.com/nitrojs/nitro/blob/4b29402c13e60c3be2b5bcebaad635ab79d16572/src/nitro.ts#L45 and here https://github.com/nitrojs/nitro/blob/4b29402c13e60c3be2b5bcebaad635ab79d16572/src/build/plugins/storage.ts#L53 The first one is...

The issue is that this line fails, when some prop is already in the setupState of the component instance. But idk where e.g. the error prop in the setupState comes...

I created https://github.com/cpsoinos/nuxt-svgo/pull/442