Integration with Nuxt DevTools

[Baroshem]

The idea would be to have a similiar log added to running your application in fev if it has NuxtSecurity enabled as it is in NuxtTailwind.

The one in tailwind outputs an url where the tailwindviewer is so that it id simple for users running the app in dev with the module to access the viewer.

I have been thinking about something similar for NuxtSecurity.

My ideas:

1. Full NuxtSecurity Config
2. Enabled headers and middleware's (names) per route ang global

Let me know what you think about it :)

[Baroshem]

I would especially love to get the feedback from @vejja @dargmuesli @pi0 @danielroe @huang-julien

[dargmuesli]

Wouldn't that be something for a devtools tab? 🤩

[huang-julien]

I was thinking the same ! @dargmuesli

[Baroshem]

[Baroshem]

Do you have any ideas how this could work?

[huang-julien]

I had already used devtools/kit once. Basically you're just providing an iframe which will get a lot of devtools helpers injected. So it's really flexible

[Baroshem]

But I wonder what would be the use case for it. In terms for headers, users can see the values in the browser network tab. While for the middlewares it might be difficult to show some meaningful data because everything can be seen in the nuxt.config.

I am just not sure what value it could bring to the user.

[pi0]

Devtools tab would a be a nice idea i would say. Adding more complexity to CLI output might be nice but it also makes peole care less about information when it matters (like warns)