docs: disable transitions by default

[danielroe]

🔗 Linked issue

hotfix to work around nuxt/nuxt#15239

❓ 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I do not believe we are currently using transitions so we probably should disable these anyway. This also serves to seriously reduce a memory leak that we're looking into.

📝 Checklist

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

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit	5cb6985
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/63564d1efa3dc600085ee9ac
😎 Deploy Preview	https://deploy-preview-8434--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pi0]

LGTM. /cc @Atinux

[Atinux]

Thanks @danielroe

Shall we simply disable transitions by default in Nuxt 3? 🤔

[danielroe]

There is merit in that. They cause issues like nuxt/nuxt#13471 when many users may not be using them at all ...

wdyt @pi0?

[Atinux]

It also brings Nuxt 3 as light as possible when starting

[pi0]

Makese sense to disable transitions by default. We only need proper way to guide users to enable it back

[manniL]

I think disabling them by default is a good idea to reduce friction, as long as docs cover how to use them (e.g. with an extra section).