It's a reasonable choice to make even if I would have gone the other way. If you don't plan on supporting this library long term or if you think that the node

It's a reasonable choice to make even if I would have gone the other way. If you don't plan on supporting this library long term or if you think that the node ecosystem isn't going to be long lived then why cause pain now in order to be compliant with the RFC? Right now it can match the browser bug and not confuse web designers moving to doing server side code thanks to Node. It is just a single colon, but in my experience this kind of debate comes up early in an ecosystems development and the decisions, especially ones that get a lot of attention, set the culture's direction pretty quick. I don't think it's a good idea long term but it's not my library so it's not my call, and I can see the pragmatism behind the authors choice.