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
We can easily make Vuestic as rollup/vite plugin. It gives more control of user development experience with compilation step.
Features:
CSS layers (I've done it before) - fix for issues when vuestic styles have more importance over tailwind - easy
Extended config support - automatic TS type generations. Similar to Nuxt types generations. - medium
Components auto-imports
We have unplugin-auto-imports and nuxt is kind of solving this problem on it's own. - medium
In-Component tree-shaking - remove some features from component if it is not used - something similar to feature flags. Not sure if it is possible to make automatic. - hard
Global config without defaults. Replace defaults with values from vuestic.config.ts - easy
Built-in devtools - hard
Auto sync colors from vuestic.config.ts with Tailwind or UnoCSS (without cli) - medium
The text was updated successfully, but these errors were encountered:
We can easily make Vuestic as rollup/vite plugin. It gives more control of user development experience with compilation step.
Features:
We have unplugin-auto-imports and nuxt is kind of solving this problem on it's own. - medium
The text was updated successfully, but these errors were encountered: