Closed harlan-zw closed 3 years ago
FYI, we have the npm org @windicss, so many we can have @windicss/webpack-plugin-vue
or `@windicss/webpack-loader-vue
. /cc @voorjaar
FYI, we have the npm org @windicss, so many we can have
@windicss/webpack-plugin-vue
or`@windicss/webpack-loader-vue
. /cc @voorjaar
I think this will be the best path forward actually. I didn't want to make it confusing to other developers which package should be used but I think this can become clearer once the other one is up and stable.
Will keep this closed for now*.
Sorry for the delay. I just discussed with my team member, we think most of your ideas are great, but we want to modify a bit. vue-windicss-webpack-plugin
is unnecessary, we want a windicss-webpack-plugin
that support vue, react, svelte at the same time. But you can support vue first, then the others. if this works for you, then welcome to join. And I will archive the vue loader. @loonpwn
Hey @voorjaar
Firstly, thanks for adding me to the org.
Was wondering if you'd be open to the idea of having someone take over the core development of this package?
The package is great and will likely be a dependency of a lot webpack-based Vue frameworks (Nuxt v2, vue-cli, etc). However for it to scale to these frameworks and reach further adoption, I feel like this package needs quite a bit of work.
In my mind that work would look like
For the last point, I think it would make sense to do one of the two (when the implementation is ready):
a. We create a new package called
vue-windicss-webpack-plugin
and we deprecate this one b. We rename this package tovue-windicss-webpack-plugin
vue-windicss-preprocess
is a bit too ambiguous at the moment and doesn't limit the scope of what the package is trying to accomplish.If all sounds good to you, would be great if I could get elevated permissions to this package and permission on npm to handle the release (username: harlan_zw).
Thanks either way and look forward to contributing where I can.