From 74b0ee6a033375a014029a105567ce4bd2c16cbf Mon Sep 17 00:00:00 2001
From: Vasyl Nahuliak <40458927+vasylnahuliak@users.noreply.github.com>
Date: Sun, 10 Nov 2024 17:44:53 +0200
Subject: [PATCH] docs: fnm configuration

---
 docs/configuration.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index 4b4c9452..dbed2f91 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -282,7 +282,7 @@ Provide an [**rc**](https://www.baeldung.com/linux/rc-files) file, which is actu
 Use cases:
 
 - You have a GUI program that runs git hooks (e.g., VSCode)
-- You reference executables that are accessible only from a tweaked $PATH environment variable (e.g., when using rbenv or nvm)
+- You reference executables that are accessible only from a tweaked $PATH environment variable (e.g., when using rbenv or nvm, fnm)
 - Or even if your GUI program cannot locate the `lefthook` executable :scream:
 - Or if you want to use ENV variables that control the executables behavior in `lefthook.yml`
 
@@ -330,6 +330,10 @@ In the rc file, export any new environment variables or modify existing ones.
 export NVM_DIR="$HOME/.nvm"
 [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
 
+# An fnm way
+export FNM_DIR="$HOME/.fnm"
+[ -s "$FNM_DIR/fnm.sh" ] && \. "$FNM_DIR/fnm.sh"
+
 # Or maybe just
 PATH=$PATH:$HOME/.nvm/versions/node/v15.14.0/bin
 ```