Releases: AngelMunoz/NvmFs
v0.9.0
This is a small release, it updates the tool required version to net8.0
It also adds some fallback mechanisms to download node if for some reason dotnet's HttpClient can't connect to the node server (it tends to happen in linux/macos) so if that fails we'll try the current tools in the OS in the following order
- curl
- pwsh
- wget
Full Changelog: v0.8.1...v0.9.0
v0.8.1
Fix EACESS symlink
error due unix permissions wrongly set in the symlink used to match the current version
Full Changelog: v0.8.0...v0.8.1
v0.8.0
What's Changed
- Updated to use FSharp.SystemCommandLine by @JordanMarr in #2
- Fix Unix Crashes by @AngelMunoz in #3
New Contributors
- @JordanMarr made their first contribution in #2
- @AngelMunoz made their first contribution in #3
Full Changelog: v0.6.0...v0.8.0
Update to .NET6
Hello there!
This is an out of nowhere update to nvmfs this version migrates .NET6 so it should bring slightly better performance (I don't think it is noticeable though we weren't doing anything that heavy)
This version brings a slightly behavior change for Windows Users
In v0.5.1 when you used --default true
or use --node <version>
on windows we would set the PATH
env variable by hand so you could have it running as soon as possible, this had a slightly undesired behavior in .NET Environment APIs the PATH is already expanded so that meant we were setting the PATH with the expanded values rather than the original variables.
we now set the NVMFS_NODE
and NVMFS_HOME
environment variables to the User's variables and we output a message telling you that you have to update your path manually to avoid that previous behavior which could be undesirable in some cases
for *nix users we're still using ~/.bashrc
let us know if we should consider other forms to do this instead
Fix list
this release fixes an issue with windows not listing versions properly
It's Alive
v0.5.0 add readme