You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the npm version's binary is libyear-npm. Maybe this version should have a more specific binary name too?
This could leave the libyear binary name available for a future project that knew how to run all of the various specific libyear-*s and aggregate them :-)
The text was updated successfully, but these errors were encountered:
Closed by release 0.2.0. Going forward please use libyear-bundler.
This could leave the libyear binary name available for a future project that knew how to run all of the various specific libyear-*s and aggregate them :-)
I noticed that the npm version's binary is
libyear-npm
. Maybe this version should have a more specific binary name too?This could leave the
libyear
binary name available for a future project that knew how to run all of the various specificlibyear-*
s and aggregate them :-)The text was updated successfully, but these errors were encountered: