fnm
fish-shell
fnm | fish-shell | |
---|---|---|
62 | 320 | |
15,710 | 24,714 | |
- | 1.4% | |
6.7 | 9.9 | |
4 days ago | 5 days ago | |
Rust | Rust | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
fnm
-
How to beautify java code reliably
Install nodejs: (I highly recommend using a node version manager like fnm) and to install a recent node version (current long term support is 16+)
-
Effective nodejs version management for the busy developer
I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.
-
Oh My Zsh
I switched from nvm to fnm a few years ago and have never looked back. Zero performance issues and it supports .nvmrc files.
https://github.com/Schniz/fnm
-
Cannot Create Next App On Windows
Are you using some kind of node version manager like fnm?
-
Pyright slows down my terminal, trying to speed it up, am using Lazyvim
If it's your terminal that's slow in general and not neovim specifically I found that switching from nvm to fnm for managing node significantly faster at starting up my shell. I don't know whether this is what your issue is but I thought I'd share it regardless. https://github.com/Schniz/fnm
-
Everything I Installed on My New Mac
fnm is a fast and simple Node.js version manager. It's really easy to use and is much faster than nvm.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
Any plans to update Pop base?
Install something like Fast Node Manager from https://github.com/Schniz/fnm and install your Node from there. I work in the software field and tend to use the LTS releases for the TypeScript/React projects I work on.
-
Comparing the Best Node.js Version Managers: nvm, Volta, and asdf
fnm!
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
Youβll need pnpm and Node.js installed on your machine + some tool for switching node versions (e.g. fnm or nvm will work fine);
fish-shell
-
FAQ on the xz-utils backdoor β via a project dev
Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.
https://github.com/fish-shell/fish-shell/releases/tag/3.7.1
https://github.com/fish-shell/fish-shell/issues/7772#issueco...
https://gitlab.archlinux.org/archlinux/packaging/packages/fi...
- Oh My Zsh
- Proposal for porting fish-shell from C++ to Rust
-
Converting the Kernel to C++
A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123
An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust
It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123
-
Day 5 - More or less...
We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.
-
Fish β Update on the Rust Port
They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.
[1] https://github.com/fish-shell/fish-shell/pull/9512
- Devuan γ’γγγ°γ¬γΌγ: 4 γγ 5 Daedalus γΈ
What are some alternatives?
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
powerlevel10k - A Zsh theme
volta - Volta: JS Toolchains as Code. β‘
starship - βποΈ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
nushell - A new type of shell
n - Node version management
oh-my-fish - The Fish Shell Framework
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
nodenv - Manage multiple NodeJS versions.
tokyonight.nvim - π A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.