fvm VS asdf

2.2 - FVM

Repositorio Github

For Flutter, if you're not working on other projects you can just downgrade your installation to the same version used on the course using the flutter channel command on the command line. If you have other projects then you can use FVM to manage multiple versions of Flutter.

I'm a frontend developer and recently have some work to do with Flutter, need to switch Flutter version in different projects. For Nodejs we have nvm to manage and switch node version. I've tried the dart-version fvm, but it does not work similar to nvm. So I released a shell-version fvm. Anyone who needs to work with multi flutter version and run into problems with dart-version fvm can have try with this.

fvm had a similar issue. This was the commit that fixed it, FYI: https://github.com/fluttertools/fvm/pull/324/files

I think the best and easiest way to change flutter version is Flutter Version Manager.

Last week I was eager to check out a little Flutter application built by Lucas Schuster. I was especially interested in trying the Flutter Desktop support for Linux. After installing Flutter via fvm, I checked out his Git repository and issued the following command for building the Flutter app on Linux:

It is good when you are can get updates and bug fixes of libs and Flutter. If anyone will try to build your project on older Flutter version, they can install something like FVM of provide path no new version of framework manually.

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/

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.

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).

(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.

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:

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.

I use the asdf version manager.

You might check out rtx[1]

Its an asdf[2] rewrite, in rust, that can do most of the things nvm can

[1] https://github.com/jdx/rtx

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