Github user merrimanr commented on the issue:
    I think we are on board with switching to yarn so no concerns there.  There 
was a discussion on it but if anyone now feels differently, speak up.
    Sounds like we still have a lot of work to do.  I would suggest reviewing 
the metron-config and metron-alerts READMEs and update them appropriately.  In 
fact, I would just search the whole project for npm commands and switch to yarn 
as needed.  You will definitely need to run this up in full dev and verify 
everything works.
    Our maven front end plugin will also need to be reviewed and updated:  We use that in 
metron-config and metron-alerts.


Reply via email to