vejja
vejja
> Just removing the line resolves the issue. I am wondering why it was added in the first place. Could you give some insights? That is a very valid remark....
> Before implementing a fix, I created a discussion in the nuxt repo to verify if context sharing is expected behavior: [nuxt/nuxt#28340](https://github.com/nuxt/nuxt/discussions/28340) It rings a bell. I remember I had...
Hey @P4sca1 Sorry, I hadn't seen your PR. Will merge both
Hi @gpataciertocom It is true that the ‘driver’ key of the ‘rateLimiter’ cannot be modified by the runtime hook. @Baroshem do you think we could support changing this? also quick...
After further review of the source code, I'm not sure we need to change the codebase to allow this functionality. It should be possible to use the standard `runtimeConfig` key...
Wonderful ! This will allow you to also pass username and password. Please have a look at the official Nuxt documentation to make sure the variables are injected in production...
We can support it, no problem I think
@dargmuesli it was just a simple type modification Happy to get your feedback on whether `require-trusted-types-for` has the right type definition. Not clear to me if the spec says that...
Hi @danielroe How would you lazy load on first request?
@tugcekucukoglu Nuxt-Security team here As discovered by @lawren in https://github.com/Baroshem/nuxt-security/issues/564, the problem arises because you (or other 3rd-parties) are mutating the Typescript definitions of the nitro renderer: ```ts export interface...