Replies: 2 comments 3 replies
-
I would really like to get some fixes like this so a new release would be great. Or at least some timeline on when we can expect the new release |
Beta Was this translation helpful? Give feedback.
-
Hey all. Indeed depcheck is widely used but depends on me as the only “maintainer”. I haven’t had the time to update the CI away from Travis to gha for releases. Once that is setup releases will come faster. Truth is, I have a job and a lot going on in my life right now and all of that takes a lot of time. On top of that I don’t really do any js work these days… depcheck started as a fun hack one night before webpack was a thing, these days there are so many things going on in this place that it’s quite hard to keep up… Depcheck had other maintainers in the past but they come and go, I have failed to create a community of people willing to work on it on their free time. All this to say, I will try and fix the CI next week and get a release for y’all. I can’t this week, I am on PTO. |
Beta Was this translation helpful? Give feedback.
-
depcheck
has not seen a release in a while and it would be great to get an idea about how the upgrade path would look like.First, some observations:
master
since and would benefit 1.x users in a drop-in updatesemver-major
is addressed in chore: downgrade sass to unbreak node 10 #798>=10
. v10 reached EoL 2021-04-30 and has fallen out of useSo with that in mind, this would make sense to me:
1.5.0
based on currentmain
(with any breaking changes addressed/reverted/omitted)node.engines
to^12.22.12 || ^14.19 || ^16 || >=18
2.0.0
Then:
npm audit
issues, security advisories, bug fixes, stability updates and likelier to have less duplicated dependency versionsdepcheck@^1
v1
can be fully deprecated and users pointed tov2
v3
release,v2
can be kept as a maintenance/support target only receiving security updates and the occasional dependency bump.Beta Was this translation helpful? Give feedback.
All reactions