docs: warn directives must be registered on both server/client

[danielroe]

🔗 Linked issue

resolves #14568

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This adds a warning to the docs that directives need to be registered on both client/server

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
Nuxt Docs	Edit on Studio ↗︎	View Live Preview	6793cfa

[sadeghbarati]

justintaddei/v-wave#351

getSSRProps(binding, vnode) {
    return {};
}

I see this workaround for SSR directives in Nuxt3, even if I add this workaround, I still have to create another directive on the server?

[danielroe]

No, you don't have to create another directive. It's not a workaround either, it's just how Vue 3 directives work with SSR.