fix: add missing useAppConfig export for non-auto-import users

[KazimirPodolski]

🔗 Linked issue

❓ 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)
• ✨ 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

Re-exports useAppConfig for those of us who is not fond of auto-import magic.

📝 Checklist

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

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@5658

commit: 14f0f69

[benjamincanac]

I don't think we should expose useAppConfig from @nuxt/ui export, we should instead add "./vue/composables" and "./vue/composables/*" exports inside package.json.

[KazimirPodolski]

I don't think we should expose useAppConfig from @nuxt/ui export, we should instead add "./vue/composables" and "./vue/composables/*" exports inside package.json.

I tried that initially but it wasn't exported properly during my local testing... I'll try again, probably I made a mistake somewhere.

[benjamincanac]

I'm not even sure this export is needed actually, you should be able to import it like this: import { useAppConfig } from '@nuxt/ui/runtime/vue/composables/useAppConfig.js'

[KazimirPodolski]

It works! Hovewer Webstorm is unable to do it automatically:

[benjamincanac]

Your screenshot made me realize the changes I just made in #5213 will break this import 😬

[benjamincanac]

@KazimirPodolski Do you have an error when importing from @nuxt/ui/runtime/vue/composables/useAppConfig.js?

[KazimirPodolski]

In Webstorm - no, in runtime - gonna check later today, I have some heavy changes ongoing.