generated from unplugin/unplugin-starter
-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching to monorepo #95
Comments
Exciting road map, but it doesn't seem like the branches are open |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey; as Pinceau has grown into the theming engine for
@nuxt-themes
org, I would like it to be a bit more modulable in its usage and project dependencies impact.The plan for me is to convert the big Vite plugin that Pinceau is right now into a set of smaller plugins splitted that way:
@pinceau/theme
@pinceau/static
css()
static features and transforms, still allowing to use Pinceau with 0kb of JavaScript code added to your project@pinceau/runtime
computedStyles
,variants
andcssProp
and add the Pinceau runtime engine to your project@pinceau/nuxt
pinceau
There would probably be a
@pinceau/shared
package in between all these "user-facing" ones that would share bits of codes and typings between all these other packages.Also, this is a very great opportunity to add a test suite for each package, that will improve the stability of Pinceau and the coherence of its feature set by a lot.
This indeed is a big piece work, that already has started in the https://github.com/Tahul/pinceau/tree/feat/rewrite-engine branch :)
The text was updated successfully, but these errors were encountered: