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
Split project #503
Comments
It’s a good idea to split packages on npm, but you should keep all the code base in the same repo, in order to make maintenance more easy. Rework split in the past and it was a pain to update all packages… |
@MoOx Good idea about keeping it all in the same repo. That should not introduce the problems rework had. |
The only project with one repo is using master in Small note: ouh, I am soo miss Bundler in node.js. GitHub |
First tests show that we can reduce core for client-side from 30 KB to 10 KB. |
Good idea! |
Ideally I'd prefer an arbitrary function syntax for plugins without the need to pull in a package, e.g. module.exports = function () {
return function (style) {
// traverse & modify style
}
} This would make it easier to intererop with other CSS bundlers, such as sheetify. ✨ |
@yoshuawuyts first version of PostCSS has simple function API too, but here is a reason why we use more complicted way. If you can fix them in different way, we can change API:
|
ah, yeah 2 + 3 make a lot of sense. Perhaps an api that looks like this could work for this case: module.exports = function (meta) {
meta({ name: 'rebecca-purple' })
return function (style) {
// traverse & modify style
}
} or module.exports = function (css) {
css('rebecca-purple', function (style} {
// traverse & modify style
})
} |
In 6.0 @yoshuawuyts Why you do not like this solution? |
Actually that sounds great, happy to see that happen ^^ |
I thinking of splitting project to:
postcss-ast
with nodes classes.postcss-css
with default parser.postcss-plugin
with API for plugins.postcss-utils
withvendor
andlist
.postcss-process
withResult
,Processor
, etc.postcss-map
with source map support.Of course, just
postcss
wwill contain all of them with same API.As result:
source-map
library is too big.The text was updated successfully, but these errors were encountered: