-
Notifications
You must be signed in to change notification settings - Fork 47
fix #17: add a stream output option #51
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
Conversation
* ensures that the transform is called on each file * ensures the default class names contain folder names
b/c tape internals are nice :)
The `bundle` now emits a `’css stream’` event. Users can listen to this and get a stream of the compiled CSS. I’m not a super big fan of this API, but I couldn’t think of a better way to give access to the stream.
Looks good! I suppose another way would be to add to the
Thoughts on pros/cons of either approach? |
True! I kinda like attaching things to |
Sure, that's a fair point. I am also not terribly fussed either way. Before we go ahead, do you know of any other plugins that emit their own custom events from |
Heh… without going on a search, the only one I know of is my own remapify :) |
Heh cool :) Will merge this for now. When we come to finalize the 1.0 release I'd like to find concrete usage examples to account for every feature, and make sure we have a consistent API. So we might want to revise it then. Thanks! |
fix #17: add a stream output option
Published v0.10.0 |
Cheers. BTW, if you're ever looking for more maintainers, I'd be happy to lend a hand. |
Thanks! I'd like to add more maintainers when we finalize our v1.0 plans, so we'd definitely love to take you up on your offer :) Will let you know when that starts moving. |
The
bundle
now emits a’css stream’
event. Users can listen to this andget a stream of the compiled CSS.
I’m not a super big fan of this API, but I couldn’t think of a better way
to give access to the stream.
fixes #17