toni

That sounds great @WhiteCollarParker, for my project it would definitely be relevant!

For me it doesn't work with Nuxt Bridge. As soon as I add `middleware: ['auth']` to router in `nuxt.config.js` like so: ```js router: { base: '/', middleware: ['auth'], linkActiveClass: 'active',...

@bmulholland yes will do, thanks!

Hey @TimVanHerwijnen, thanks for digging in! I just raised the issue in the Nuxt repo (nuxt/bridge#164) and created a reproduction: Github: https://github.com/toniengelhardt/nuxt-bridge-debug CodeSandBox: https://codesandbox.io/s/cool-benji-c0ryp Note that the router config also...

**Update** The previous issue has been fixed in Nuxt Bridge, but now I get this one: I think that is because the middleware is now actually loaded, but not compatible...

Interesting, so it probably is a Vite bug. I also have other errors when disabling Vite in my project, but I'll try to resolve and confirm that it works without...

Also having this problem with the latest `bridge-edge` and `auth-next`: ```bash Internal server error: Failed to resolve import "{path}/frontend/middleware/auth" from "defaultexport:{path}/frontend/.nuxt/middleware.js". Does the file exist? ``` What's compiled to `middleware.js`...

Here is a reproduction of the problem: https://stackblitz.com/edit/nuxt-bridge-test?file=nuxt.config.ts @bmulholland, just to confirm, it is currently not possible to upgrade to Bridge when using nuxt/auth right?

> While we're waiting on the nuxt/auth rewrite, I have deployed the current auth module to production with nuxt bridge and that's working well. Closing this issue as resolved. @bmulholland...

Thanks @moritzruth, your solution works for me.