We had an issue with the npm project / github being removed, breaking the build
We're using a fork of an older version, we might be forking that again to make the style match
Is this the solution we want? Will this break again? What's the general strategy for npm project dependency removal (for the short term build break, for the long term maintenance)?
No perfect answer
One possible solution: fork everything - this isn't reasonable
We're using a fork of Perfect Scrollbar that's now unmaintained - this was risky to start with!
One way to avoid the volatility is to use official packages
We're now using someone else's fork - still not the official package.
We're likely using this because it was the easiest way to make it work.
The new unofficial package will not be maintained, however he has promised that it won't go away.
How often do we think we've done this (i.e. using something that's unmaintained or unofficial)?
Maybe there was another package, name changed, links, etc
Is this related to some of the warnings we saw in GitHub?
we think no, the warnings may be more security issues and upgrades available.
we have tickets/issues in the backlog that we need to get to
Klaudia Pałkowska (Deactivated) and Josh Zamor to revisit how to bring upgrades / selecting package versions for release into our normal dev flow (perfect scrollbar notes above for reference)
Josh Zamor: look at if I can host it on Google Meet
Paulina Buzderewicz and Josh Zamor to bring up the timing question on fixing the HMIS flows (Measure and MeasureReport) on the COVID call Thur.