Skip to content

Conversation

jd-solanki
Copy link
Contributor

@jd-solanki jd-solanki commented Sep 17, 2025

πŸ”— Linked issue

None

Here's the playground link: https://nuxt-ui-playground.netlify.app/

❓ 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

For Nuxt UI playground we are using Vue Repl. It requires lib to have compiled components in ESM so we can import them via import map: vuejs/repl#234 (comment)

Hence, added new build setup that compiles components using vite.

πŸ“ Checklist

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

@benjamincanac
Copy link
Member

@danielroe Do you know if there's a way to achieve this through the current build process? πŸ€”

@danielroe
Copy link
Member

I would guess it would significantly increase the build size. but if that's not an issue, you can likely add each component as an 'entry' (using a globbing util to get them all) in build.config. you will also need to ensure that rollup-plugin-vue (or vite-plugin-vue) is added to the rollup config, which might have to be in an unbuild hook, if there's no option to do so directly.

Copy link
Member

Doesn't the build size increases with both solutions? We would need to publish the result of this build as well no? πŸ€”

@jd-solanki
Copy link
Contributor Author

@danielroe @benjamincanac

How about distributing it as a separate package? This is only needed for the playground. Maybe like @nuxt/ui-esm?

BTW, the goal is that it shouldn't affect existing build & distribution.

@benjamincanac benjamincanac force-pushed the v4 branch 2 times, most recently from 3f0c24a to c9ba808 Compare September 23, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v4 #4488
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants