v0.1.0

⚠️ Breaking Changes

The server resolver must now be bind to the event.context using the request hook.

Before

export default defineNitroPlugin((nitroApp) => {
  nitroApp.$authorization = {
    resolveServerUser: () => {
      return { id: 2, name: 'User 1' } satisfies User
    },
  }
})

After

export default defineNitroPlugin((nitroApp) => {
  nitroApp.hooks.hook('request', async (event) => {
    event.context.$authorization = {
      resolveServerUser: () => {
        return { id: 1, name: 'User 1' }
      },
    }
  })
})

Using the event.context is recommended to attach custom properties (instead of the nitroApp).

compare changes

🚀 Enhancements

• Export types (8472ede)

🩹 Fixes

• Make component prop args optional (27d51b2)

💅 Refactors

• ⚠️ Prefer event.context instead of nitro-app (57345df)

📖 Documentation

• Explain usage with v4 and fix component props (ffc1c4e)
• Update usage with nitro (e1a48c6)

🏡 Chore

• Remove exclude in tsconfig (0980005)
• Update deps (515ed7a)
• Remove a log (9572561)
• Update playground (57ea855)
• Update lockfile (df72014)

✅ Tests

• Components (b7a6b74)
• Remove component prop args (31f1dd4)

🤖 CI

• Install playwright (a6b08f9)

⚠️ Breaking Changes

• ⚠️ Prefer event.context instead of nitro-app (57345df)

❤️ Contributors

• Barbapapazes e.soubiran25@gmail.com