fix: import nuxt composables from #imports

[danielroe]

Changes

This is a DX improvement when developing - we can avoid loading the entire barrel file at #app by using the new granular imports merged in nuxt/nuxt#23951.

Checklist

• Tests for new code (see advice on the tests we use)
• Accounted for the impact of any changes across different browsers

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[posthog-bot]

This PR was closed due to lack of activity. Feel free to reopen if it's still relevant.

[danielroe]

Hm.

[GalacticHypernova]

Bad bot, reopen this PR right this instant!

[GalacticHypernova]

@pauldambra perhaps you can merge this? There's no reason not to, it's a DX improvement with no downsides.

[pauldambra]

Hey,

Coincidentally, we've just set up a bot so we don't miss external contributions like this... sorry for the silence!

I've never used nuxt. I'll need to checkout the playground example before and after just for a check.

[pauldambra]

TestCafe is failing but that's ok since it's a fork and if this change can break the SDK (and I can't even imagine how it could) then I'd want to find out 🤣

Sorry again for missing this! Thanks for taking the time to update it

[danielroe]

Not at all 😊