The Collections library has a large backlog of issues pertaining to compatibility with the ES6 spec that emerged after this library was created. These issues cannot be addressed without breaking backward compatibility with Montage.
There is a path forward where we create a new Collections monorepo and publish @collections organization packages for each collection or another path forward where we rip the the monkey-patches out of Collections and fix everything that breaks in Montage and FRB. Either way, this library needs volunteers. I’ve attached a form requesting volunteers from the Collections community, what they need, what they can provide. I would like to hear suggestions.
Although I contributed this library to the Montage project, I do not own the project and do not make decisions about its future. My attention is also quite distant from this project. I however view this package as a commons for the JavaScript community, sitting on a very authoritative name in npm. I would like to rally support to improve the health of the collections ecosystem.
The Collections library has a large backlog of issues pertaining to compatibility with the ES6 spec that emerged after this library was created. These issues cannot be addressed without breaking backward compatibility with Montage.
There is a path forward where we create a new Collections monorepo and publish
@collectionsorganization packages for each collection or another path forward where we rip the the monkey-patches out of Collections and fix everything that breaks in Montage and FRB. Either way, this library needs volunteers. I’ve attached a form requesting volunteers from the Collections community, what they need, what they can provide. I would like to hear suggestions.https://docs.google.com/forms/d/e/1FAIpQLSd4j9-Uwy4Yoc9djU9Yh6RyhucjDhoyG58N4Fck7OZgHAtL-Q/alreadyresponded?c=0&w=1
Although I contributed this library to the Montage project, I do not own the project and do not make decisions about its future. My attention is also quite distant from this project. I however view this package as a commons for the JavaScript community, sitting on a very authoritative name in
npm. I would like to rally support to improve the health of the collections ecosystem.