Ask HN: Why does every package+module system become a Rube Goldberg machine?

Re:Ask HN: Why does every package+module system become a Rub... by mijoharas on Monday January 30, 2023 @09:57AM (#34580351)

Not a generic package manager, but it's probably worth calling out asdf as the generic version manager[0] (maybe you're already aware of it, but it's a generic replacement for nvm, rvm, virtualenv, *vm, which supports any language based on plugins.)

Again, maybe you're already aware of it, but I think it's a nice example of genericising a concern common to many languages which sounds similar to what you're asking for (albeit unfortunately in a slightly different space).

[0] https://github.com/asdf-vm/asdf

[ Parent | on HN ]

Re:Ask HN: Why does every package+module system become a Rub... by dmix on Monday January 30, 2023 @10:57AM (#34581406)

At a minimum it's useful having the `.tool-versions` dotfile in a project directory which lists the versions of each language, db, and package manager version (our Rails project lists versions for ruby, bundler, postgres, node, yarn, redis). Even if all devs don't use asdf, it's a useful reference point.

https://asdf-vm.com/manage/configuration.html#tool-versions

Similar to an `.editorconfig` to globally define stuff like tab widths for IDEs.

[ Parent | on HN ]