Hiya! Is there any interest in having https://github.com/clj-commons/antq find outdated dependencies in your package.json files? If so, please chime in on the https://github.com/clj-commons/antq/issues/412!
Left a huge comment. Dunno, maybe I’m just grumpy today (well, more than usual anyway), but the whole discussion feels to me like the OP is a drive-by LLM enthusiast. Maybe a genuine antq user with a genuine need, but the whole research and discussion don’t feel that way - just a bombardment of info bits with little to no substance behind them.
Thanks for the feedback, @p-himik. The author https://github.com/clj-commons/antq/pulls?q=is%3Apr+state%3Aclosed+author%3Aaadrian. I’m pretty sure they’re a legit Antq user. I don’t know if they use LLMs (this issue felt like it to me but 🤷). Thanks for teaching me a new term: https://en.wikipedia.org/wiki/Gish_gallop
I like keeping with the unix philosophy, in do one thing and do it well. There are already existing tools out there (e.g., npm-check-updates), that are maintained, well understood and used widely in the “frontend” space. I would prefer keeping antq focused on the Java world.
One only has to look at the documentation for npm-check-updates (https://github.com/raineorshine/npm-check-updates), to see what antq would have to do, in order to achieve a degree of partity, or semi-usefulness.
I chimed in too since we have to deal with node/yarn/expo at work and it sucks—and I don't think this would actually improve anything.
Does antq support upgrading Gradle dependencies?
No, only checking them. See https://github.com/clj-commons/antq#opt-check-gradle and https://github.com/clj-commons/antq#supported-files
Oh wow, I had not realized it supported so many things now. Only reporting outdated could be an avenue for npm as well no? Though I agree it sounds maybe there's not a clear path for properly supporting that behavior for JS
Yeah, go read the issue in detail: it explains why that is both problematic and likely not in scope for antq…