Jakub Hampl

I would definitely use this in my project. I think css colors are a de-facto interchange format for colors on the web, so if you need interop with a system...

You should probably also include keyword colors in the parser: Example using elm/parser ```elm keywords : Parser Color keywords = oneOf [ fromHexString "#000000" |. keyword "black" , fromHexString "#c0c0c0"...

Perhaps a `$runInPipeline` property for processors in addition to `$runBefore` et al? Then dgeni would construct a directed graph satisfying those constraints?

I thought I would chime in as I'm using Dgeni in a perhaps slightly different manner than it was originally intended and hence I've been working on my own ecosystem...

Added sparse arrays option in a recent commit

May I point you to https://github.com/hayleigh-dot-dev/elm-package-prefixer? That's generally a great way to solve this problem for your specific combination of packages without needless wrapping for everyone else.

In the meantime I used some random web scraper tool: http://fetchrss.com/rss/5eb533528a93f8d7638b45675eb533288a93f80d628b4567.atom No idea how well it will work, but it's a workaround...

One point for the latter is that it can be quite nice to use it to conditionally add elements to lists: ```elm [ some , list ] |> Maybe.Extra.fold (::)...

Yes at least for the attributes. If one would give the values (i.e. the various keywords and units) this treatment, then that would be a breaking change.

[Here's an Ellie](https://ellie-app.com/3MZ7rrSjpQRa1/0) showing using z-index for showing shadows over a neighboring layer.