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
I want to write a package to dedupe CSS; all of it. Problem is: we can't access the whole bundle because we stream it out. Should we perhaps introduce a plugin system of the sorts and have a labeled pipeline thing like browserify does? Perhaps only allow access to the final output stream?
cc/ @ahdinosaur@hughsk thoughts on how we can apply transformations to all of the CSS? Thanks!
the simplest option feels like a "global plugin": a function to create a transform stream that is piped the final output stream, but happy with whatever you think is the best way to support your use case. 🌸
Yeah, think so too - tho in on the other hand Browserify is super mature
and their plugin design is well thought out; perhaps we should make the
leap and copy it? idk
On Sat, Jan 14, 2017 at 5:11 AM Mikey ***@***.***> wrote:
the simplest option feels like a "global plugin": a function to create a
transform stream that is piped the final output stream, but happy with
whatever you think is the best way to support your use case. 🌸
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWleh421IPhbWcG2jqxu9e6ndUg_DbRks5rSEsCgaJpZM4LjfNH>
.
Activity
yoshuawuyts commentedon Jan 14, 2017
This was brought up by dat-ecosystem-archive/datBase#381, which shows we need to dedupe - best would be to operate on all of the CSS ghmm
ahdinosaur commentedon Jan 14, 2017
the simplest option feels like a "global plugin": a function to create a transform stream that is piped the final output stream, but happy with whatever you think is the best way to support your use case. 🌸
yoshuawuyts commentedon Jan 14, 2017