@Angle
And good practice & good outcome for you (and community) if you split your project libs out into deps that you use. Means people can use your foo lib outside of foo meteor app. You might even get submitted improvements from doing that! Whereas if bundled, the lib won't be readily useable by another project.
Notices by chris burgess (xurizaemon@mastodon.social)
-
chris burgess (xurizaemon@mastodon.social)'s status on Tuesday, 24-Apr-2018 18:15:45 EDT chris burgess -
chris burgess (xurizaemon@mastodon.social)'s status on Wednesday, 11-Apr-2018 02:53:36 EDT chris burgess @xurizaemon @strypey @arunisaac
OS updates don't always mean you need to update the tools that run on it. Even rebuilding for a new OS release might leave nothing in your commit log.
I hear what you're asking for though, and I do myself assess projects by some combination of community / source activity before using them ... I just don't know if that formula can be applied evenly across projects. Or even articulated!
-
chris burgess (xurizaemon@mastodon.social)'s status on Monday, 06-Nov-2017 23:38:29 EST chris burgess @strypey "Something is wrong on the internet – James Bridle – Medium"
https://medium.com/@jamesbridle/something-is-wrong-on-the-internet-c39c471271d2