You might want to take a quick look at Showcase.
kitty
terminal: See extras forkitty
config- a nerd font
node
: I recommend using a node version manager, like fnmpython3
: If you're on Linux, chances are it's already installed by defaultneovim
: Either build from source or use appimage (v0.10
or newer)- a clipboard manager (e.g.
xclip
) and - and some other minor dependencies (see below)
sudo apt install git build-essential python3-venv xclip fd-find ripgrep -y
npm install -g yarn
npm install -g typescript
npm install -g @vue/typescript-plugin # only needed for vue projects
Recommend: Symlink nvim.appimage to nvim
mkdir -p ~/Applications
mv ~/Downloads/nvim.appimage ~/Applications
chmod u+x ~/Applications/nvim.appimage
sudo ln -s ~/Applications/nvim.appimage /usr/local/bin/nvim
For debian-based distro, you need to symlink fd-find to fd
# Make sure `bin` folder exist
mkdir -p ~/.local/bin
# Symlink `fdfind` to `fd`
ln -s $(which fdfind) ~/.local/bin/fd
# Add `.local/bin` to `$PATH` (change zshrc to whatever shell you're using)
echo "\n# Add .local/bin to PATH" >> ~/.zshrc
echo "export PATH=\"$HOME/.local/bin:\$PATH\"" >> ~/.zshrc
- Backup your current neovim config (if any)
curl -fsSL https://raw.githubusercontent.com/xuanhung1509/nvim/main/scripts/backup.sh | bash
- Clone the repo
git clone https://github.com/xuanhung1509/nvim.git ~/.config/nvim
- Start neovim
nvim
-
eslint
: For projects with mixed config formats (e.g. monorepo), a file in folders with old config format has to be open first. If you open a file in folders with new config format first, opening a file in folders with old config format afterwards would raise an error thateslint
cannot find the config file. -
Sometimes in
vue
files, code folding takes a long time to detect fold or simply doesn't work.