fix(nuxt): prioritise vue app context when available

[danielroe]

🔗 Linked issue

resolves #20741
related #19624 (comment)
proper fix will need to come vuejs/core#7743

❓ 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

Now that we have access to hasInjectionContext we can ensure we only check for current vue instance when we are within a component (or getCurrentInstance should fail).

TODO:

• confirm that Current instance is not unset after error in data() on SSR vuejs/core#7733 doesn't cause request to be shared when using this strategy

📝 Checklist

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

[danielroe]

/trigger release

[github-actions]

🚀 Release triggered! You can now install nuxt@npm:nuxt3@pr-20910

[danielroe]

/trigger release

[github-actions]

🚀 Release triggered! You can now install nuxt@npm:nuxt3@pr-20910

[danielroe]

/trigger release

[github-actions]

🚀 Release triggered! You can now install nuxt@npm:nuxt3@pr-20910

[danielroe]

The test failure we're experiencing is a validation of #15164, meaning that the Nuxt test fixture is a reproduction (cc: @pi0).

[pi0]

LGTM 💯

[pi0]

The test failure we're experiencing is a validation of #15164, meaning that the Nuxt test fixture is a reproduction (cc: @pi0).

I will test this afterwards if you can confirm only dev tests are failing for windows with 503

[danielroe]

@pi0 - Yes, that's the error code: https://github.com/nuxt/nuxt/actions/runs/5002108510/jobs/8961711745.