feat(nuxt): tryUseNuxtApp composable

[daniluk4000]

🔗 Linked issue

#24681

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 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 PR adds new tryUseNuxtApp alias for useNuxtApp which will return null instead of throwing an exception. This also matches with existing tryUseNuxt composable.

Resolves #24681

I have also decided not to create separate page in docs for this one.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
Nuxt Docs	Edit on Studio ↗︎	View Live Preview	5f7cc84

[danielroe]

Nice work.

[peteromano]

Hi guys, just curious:

Was this meant for modules and integrations? I think nuxt storybook temporarily throws this exception when booting up, and seems like this would help

[daniluk4000]

Hi guys, just curious:

Was this meant for modules and integrations? I think nuxt storybook temporarily throws this exception when booting up, and seems like this would help

Yo. I was using this for composables that can be run in modules/plugins/components/async context. This meant to be used whenever dev is OK that he could not have context currently and have alternative to use instead.

I dont know about Storybook issue, but if it needs that context, tryUseNuxtApp wouldn't help much.