zsh-nvm
asdf
Our great sponsors
zsh-nvm | asdf | |
---|---|---|
5 | 341 | |
2,149 | 20,448 | |
- | 2.8% | |
1.2 | 7.9 | |
about 1 month ago | 5 days ago | |
Shell | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zsh-nvm
- Just updated easy-npm based on community feedback
- NVM is completely broken, how can I fix it?
-
I switched from fish to zsh, because I don't like the fact that fish doesn't execute shell script, on the other hand, zsh is kind of slow to start, when I was using fish there was not delay, how could I speed zsh startup time? Here is my .zshrc: https://github.com/jgsn13/dotfiles/blob/main/.zshrc
With Zsh, nvm loading was a big time sink for me. I have it lazy loading using zsh-nvm and it’s much faster. My start up time is unnoticeable.
-
Zsh Plugins Commit TOP
nvm 🥇 💼 - ZSH plugin for installing, updating and loading nvm.
-
Setup Javascript Dev on ChromeOS
$ git clone https://github.com/lukechilds/zsh-nvm ~/.oh-my-zsh/custom/plugins/zsh-nvm
asdf
-
Install Asdf: One Runtime Manager to Rule All Dev Environments
The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.
I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.
[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...
[1]: https://github.com/asdf-vm/asdf/pull/1441
- Show HN: I made a multiple runtime version manager that can be used on Windows
-
Volta – Fastest Node version manager in Rust
Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions
https://asdf-vm.com/
-
Pyenv – lets you easily switch between multiple versions of Python
Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
-
A Journey to Find an Ultimate Development Environment
The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).
-
How to Install Your Python Version on Ubuntu
(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.
-
Beginners Intro to Trunk Based Development
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).
-
Practical Guide to Trunk Based Development
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:
- Criando seu ambiente com ASDF
-
Kotlin version manager
I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.
What are some alternatives?
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
SDKMan - The SDKMAN! Command Line Interface
zsh-autoswitch-virtualenv - 🐍 ZSH plugin to automatically switch python virtualenvs (including pipenv and poetry) as you move between directories
pyenv - Simple Python version management
termux-ohmyzsh - Colorize your termux! Oh-my-zsh included!
rbenv - Manage your app's Ruby environment
Visual Studio Code - Visual Studio Code
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
zsh-autopair - Auto-close and delete matching delimiters in zsh
volta - Volta: JS Toolchains as Code. ⚡
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
HomeBrew - 🍺 The missing package manager for macOS (or Linux)