I do not know whether you already suggest to use shrinkwrap as mandatory tool to create releases of the oasp4js. If so, we should document a release howto similar to what we have for oasp4j, which covers such mandatory steps to be performed to enable stable release management.
I do not know whether you already suggest to use shrinkwrap as mandatory tool to create releases of the oasp4js. If so, we should document a release howto similar to what we have for oasp4j, which covers such mandatory steps to be performed to enable stable release management.