You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mainly @nuxt/kit is the canonical place where useful nuxt utils should go and we usually use standard/sharable solutions across the UnJS ecosystem.
I have moved the issue from #302 PR to first think about what tools are really useful that are related to Nuxi CLI itself being exposed, and cannot go to either kit or unjs. (resolution for example is possible via mlly)
Why not exposing all utils from nuxi? It makes internal refactors and versioning harder because of breaking change chances.
The text was updated successfully, but these errors were encountered:
Context: #302 made by @stafyniaksacha initially because of nuxtlabs/nuxt-component-meta#60 (comment) to export some useful utils.
Mainly
@nuxt/kit
is the canonical place where useful nuxt utils should go and we usually use standard/sharable solutions across the UnJS ecosystem.I have moved the issue from #302 PR to first think about what tools are really useful that are related to Nuxi CLI itself being exposed, and cannot go to either kit or unjs. (resolution for example is possible via
mlly
)Why not exposing all utils from nuxi? It makes internal refactors and versioning harder because of breaking change chances.
The text was updated successfully, but these errors were encountered: