pkgx VS asdf-nodejs

I’m liking pkgx over asdf as it can activate project tooling upon cd’ing into a project folder.

https://pkgx.sh

I saw some alternatives being suggested and wanted to do the same (Also, so that I can look back at this item, through my comments :) ). Started using https://pkgx.sh/ lately. I know it has some baggage with tea.xyz and crypto, but it is also easy to get started with.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

1. pkgx

Before diving in, it's a good idea to have a package manager handy, like tea. It'll handle your development environment and simplify your life!

Direct fast-track link to repo

checkout https://github.com/teaxyz/cli and https://github.com/teaxyz/pantry

Install is tea: sh <(curl https://tea.xyz) and

I have used a similar tool asdf before, but the previous experience of using asdf was not very good (I don’t mean to step on it~, the ASDF ecosystem is very strong), vfox now supports a lot of plugins, and can already manage the versions of most common mainstream languages.

Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools.

It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.

That's what I would suggest as well. WSL2 and use asdf[1] to manage the erlang/elixir versions.

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

echo "Installing nodejs with asdf" asdf plugin add nodejs https://github.com/asdf-vm/asdf-nodejs.git asdf install nodejs latest asdf global nodejs latest

However this is still a neat script OP! I was looking for something like this when installing Go for the first time and was contemplating between goenv, gvm, and asdf before settling on brew.

Have you tried this? https://github.com/asdf-vm/asdf-nodejs#nvmrc-and-node-versio...

Also lts, lts-hydrogen, etc are available to install I can see when running `asdf list all nodejs`

How does this compare to nvm or asdf?

I'm not too familiar with installing Ruby on Mac, but you could try using a ruby version manager (like rbenv or asdf).

For more information, or if you need help on this awesome tool, don’t hesitate to head over to asdf-vm.com. Also, feel free to star the GitHub Repository of asdf to support the team behind this project. 😉

nvm was adding a huge delay to my shell startup and starting node. There are faster ones out there like n https://github.com/tj/n or fnm https://github.com/Schniz/fnm I use fnm there are also similar tools that work with multiple languages like asdf https://github.com/asdf-vm/asdf