![\"Screenshot](\"https://www.nushell.sh/frontpage/ls-example.png\")
\n\n### Nu works with existing data\n\nNu speaks [JSON, YAML, SQLite, Excel, and more](/book/loading_data.html) out of the box. It's easy to bring data into a Nu pipeline whether it's in a file, a database, or a web API:\n\n![\"Screenshot](\"https://www.nushell.sh/frontpage/fetch-example.png\")
\n\n### Nu has great error messages\n\nNu operates on typed data, so it catches bugs that other shells don't. And when things break, Nu tells you exactly where and why:\n\n![\"Screenshot](\"https://www.nushell.sh/frontpage/miette-example.png\")
\n\n## Get Nu\n\nNushell is available as [downloadable binaries](https://github.com/nushell/nushell/releases), [via your favourite package manager](https://repology.org/project/nushell/versions), in [a GitHub Action](https://github.com/marketplace/actions/setup-nu), and as [source code](https://github.com/nushell/nushell). Read [the detailed installation instructions](/book/installation.html) or dive right in:\n\n#### macOS / Linux:\n\n##### Homebrew\n\n```shell\n$ brew install nushell\n```\n\n##### Nix profile\n\n```shell\n$ nix profile install nixpkgs#nushell\n```\n\n#### Windows:\n\n```powershell\n# Install to user scope (by default).\nwinget install nushell\n# Machine scope installation (Run as admin).\nwinget install nushell --scope machine\n```\n\nAfter installing, launch Nu by typing `nu`.\n\n## Documentation\n\n* [Getting Started](/book/getting_started.html) guides you through getting familiar with Nushell\n* [Coming to Nu](/book/coming_to_nu.html) describes similarities and differences to other languages and shells\n* [Nu Fundamentals](/book/nu_fundamentals.html) is a more elaborate and structured description of the fundamentals\n* [Programming in Nu](/book/programming_in_nu.html) describes Nu as a programming language\n* [Nu as a Shell](/book/nu_as_a_shell.html) gives you insight into interactive functionality and configurability in a shell environment\n\n## Community\n\nJoin us [on Discord](https://discord.gg/NtAbbGn) if you have any questions about Nu!\n\nYou can help improve this site by [giving us feedback](https://github.com/nushell/nushell.github.io/issues) or [sending a PR](https://github.com/nushell/nushell.github.io/pulls).\n\n\n\n\n\n\nIf you'd like to retry the search, try changing the query to increase the likelihood of a match."}]}},"corr_id":"nushell-config-env-file::construct"}
{"t":"2026-08-20T00:13:10.359Z","dir":"event","kind":"fitness.destructive_call","raw":{"tool":"search_generic_documentation","confirmed":false,"status":"ok"},"corr_id":"nushell-config-env-file::construct"}
{"t":"2026-08-20T00:13:12.293Z","dir":"in","raw":{"method":"tools/call","params":{"name":"search_generic_documentation","arguments":{"owner":"nushell","repo":"nushell.github.io","query":"config.nu env.nu autoload configuration files"}},"jsonrpc":"2.0","id":20},"corr_id":"nushell-config-env-file::construct"}
{"t":"2026-08-20T00:13:12.764Z","dir":"out","raw":{"jsonrpc":"2.0","id":20,"result":{"searchQuery":"config.nu env.nu autoload configuration files","content":[{"type":"text","text":"### Search Results for: \"config.nu env.nu autoload configuration files\"\n\nNo relevant documentation found for your query. It's either being indexed or the search query did not match any documentation.\n\nAs a fallback, this is the documentation for nushell/nushell.github.io:\n\n---\nhome: true\nheroImage: null\nheroText: Nushell\ntagline: A new type of shell\nactionText: Get Started →\nactionLink: /book/\nfeatures:\n - title: Cross-platform\n details: Nu works on Linux, macOS, BSD, and Windows. Learn it once, then use it anywhere.\n - title: Everything is data\n details: Nu pipelines use structured data so you can safely select, filter, and sort the same way every time. Stop parsing strings and start solving problems.\n - title: Powerful plugins\n details: It's easy to extend Nu using a powerful plugin system.\n---\n\n- `, and others. See `nu --help` for a complete list.|\n|9.|(main)|Gets the path to `env.nu` and `config.nu`. By default, these are located in the config directory, but either or both can be overridden using the `--env-config
\n ![](\"screenshot_gui_memory_usage_graph.png\")
\n
\n ![](\"screenshot_gui_group_by_backtrace.png\")
\n
\n ![](\"screenshot_gui_scripting_console.png\")
\n
\n ![](\"screenshot_graph.png\")
\n
\n \n
\n \n
\n \n
\n \n
\n\tSpecial thanks to:
\n\n|![\"Warp](\"https://github.com/warpdotdev/brand-assets/blob/main/Github/Sponsor/Warp-Github-LG-02.png\")
Warp, built for coding with multiple AI agents
Available for macOS, Linux and Windows |\n| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n\n
\n\n## Yazi - ⚡️ Blazing Fast Terminal File Manager\n\nYazi (means \"duck\") is a terminal file manager written in Rust, based on non-blocking async I/O. It aims to provide an efficient, user-friendly, and customizable file management experience.\n\n💡 A new article explaining its internal workings: [Why is Yazi Fast?](https://yazi-rs.github.io/blog/why-is-yazi-fast)\n\n- 🚀 **Full Asynchronous Support**: All I/O operations are asynchronous, CPU tasks are spread across multiple threads, making the most of available resources.\n- 💪 **Powerful Async Task Scheduling and Management**: Provides real-time progress updates, task cancellation, and internal task priority assignment.\n- 🖼️ **Built-in Support for Multiple Image Protocols**: Also integrated with Überzug++ and Chafa, covering almost all terminals.\n- 🌟 **Built-in Code Highlighting and Image Decoding**: Combined with the pre-loading mechanism, greatly accelerates image and normal file loading.\n- 🔌 **Concurrent Plugin System**: UI plugins (rewriting most of the UI), functional plugins, custom previewer/preloader/spotter/fetcher; Just some pieces of Lua.\n- ☁️ **Virtual Filesystem**: Remote file management, custom VFS provider, custom search engines.\n- 📡 **Data Distribution Service**: Built on a client-server architecture (no additional server process required), integrated with a Lua-based publish-subscribe model, achieving cross-instance communication and state persistence.\n- 📦 **Package Manager**: Install plugins and themes with one command, keeping them up-to-date, or pin them to a specific version.\n- 🧰 Integration with ripgrep, fd, fzf, zoxide\n- 💫 Vim-like input/pick/confirm/which/notify component, auto-completion for cd paths\n- 🏷️ Multi-Tab Support, Cross-directory selection, Scrollable Preview (for videos, PDFs, archives, code, directories, etc.)\n- 🔄 Bulk Rename/Create, Archive Extraction, Visual Mode, File Chooser, [Git Integration](https://github.com/yazi-rs/plugins/tree/main/git.yazi), [Mount Manager](https://github.com/yazi-rs/plugins/tree/main/mount.yazi)\n- 🎨 Theme System, Mouse Support, [Drag and Drop](https://yazi-rs.github.io/docs/dnd), Trash Bin, Custom Layouts, CSI u, OSC 52, CSI 2031\n- ... and more!\n\nhttps://github.com/sxyazi/yazi/assets/17523360/92ff23fa-0cd5-4f04-b387-894c12265cc7\n\n## Project status\n\nPublic beta, can be used as a daily driver.\n\nYazi is currently in heavy development, expect breaking changes.\n\n## Documentation\n\n- Usage: https://yazi-rs.github.io/docs/installation\n- Features: https://yazi-rs.github.io/features\n\n## Discussion\n\n- Discord Server (English mainly): https://discord.gg/qfADduSdJu\n- Telegram Group (Chinese mainly): https://t.me/yazi_rs\n\n## Image Preview\n\n| Platform | Protocol | Support |\n| ---------------------------------------------------------------------------- | -------------------------------------- | -------------------------------------- |\n| [kitty](https://github.com/kovidgoyal/kitty) (>= 0.28.0) | [Kitty unicode placeholders][kgp] | ✅ Built-in |\n| [iTerm2](https://iterm2.com) | [Inline images protocol][iip] | ✅ Built-in |\n| [WezTerm](https://github.com/wez/wezterm) | [Inline images protocol][iip] | ✅ Built-in |\n| [Konsole](https://invent.kde.org/utilities/konsole) | [Kitty old protocol][kgp-old] | ✅ Built-in |\n| [foot](https://codeberg.org/dnkl/foot) | [Sixel graphics format][sixel] | ✅ Built-in |\n| [Ghostty](https://github.com/ghostty-org/ghostty) | [Kitty unicode placeholders][kgp] | ✅ Built-in |\n| [Windows Terminal](https://github.com/microsoft/terminal) (>= v1.22.10352.0) | [Sixel graphics format][sixel] | ✅ Built-in |\n| [st with Sixel patch](https://github.com/bakkeby/st-flexipatch) | [Sixel graphics format][sixel] | ✅ Built-in |\n| [Warp](https://www.warp.dev) (macOS/Linux only) | [Inline images protocol][iip] | ✅ Built-in |\n| [Tabby](https://github.com/Eugeny/tabby) | [Inline images protocol][iip] | ✅ Built-in |\n| [VSCode](https://github.com/microsoft/vscode) | [Inline images protocol][iip] | ✅ Built-in |\n| [Rio](https://github.com/raphamorim/rio) (>= 0.3.9) | [Kitty unicode placeholders][kgp] | ✅ Built-in |\n| [Black Box](https://gitlab.gnome.org/raggesilver/blackbox) | [Sixel graphics format][sixel] | ✅ Built-in |\n| [Bobcat](https://github.com/ismail-yilmaz/Bobcat) | [Inline images protocol][iip] | ✅ Built-in |\n| X11 / Wayland | Window system protocol | ☑️ [Überzug++][ueberzug] required |\n| Fallback | [ASCII art (Unicode block)][ascii-art] | ☑️ [Chafa][chafa] required (>= 1.16.0) |\n\nSee https://yazi-rs.github.io/docs/image-preview for details.\n\n\n\n[kgp]: https://sw.kovidgoyal.net/kitty/graphics-protocol/#unicode-placeholders\n[kgp-old]: https://github.com/sxyazi/yazi/blob/main/yazi-adapter/src/drivers/kgp_old.rs\n[iip]: https://iterm2.com/documentation-images.html\n[sixel]: https://www.vt100.net/docs/vt3xx-gp/chapter14.html\n[ascii-art]: https://en.wikipedia.org/wiki/ASCII_art\n\n\n\n[ueberzug]: https://github.com/jstkdng/ueberzugpp\n[chafa]: https://hpjansson.org/chafa/\n\n## Special Thanks\n\n\n\n|
Warp, built for coding with multiple AI agents
Available for macOS, Linux and Windows |\n| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n\n
![\"RustRover](\"https://resources.jetbrains.com/storage/products/company/brand/logos/RustRover.svg\")
\n\nThanks to RustRover team for providing open-source licenses to support the maintenance of Yazi.\n\nActive code contributors can contact @sxyazi to get a license (if any are still available).\n\n## License\n\nYazi is MIT-licensed. For more information check the [LICENSE](LICENSE) file.\n\n\nIf you'd like to retry the search, try changing the query to increase the likelihood of a match."}]}},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:35.988Z","dir":"event","kind":"fitness.destructive_call","raw":{"tool":"search_generic_documentation","confirmed":false,"status":"ok"},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:38.610Z","dir":"in","raw":{"method":"tools/call","params":{"name":"search_generic_code","arguments":{"owner":"sxyazi","repo":"yazi","query":"keymap.toml"}},"jsonrpc":"2.0","id":33},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:40.201Z","dir":"out","raw":{"jsonrpc":"2.0","id":33,"result":{"searchQuery":"keymap.toml","content":[{"type":"text","text":"### Code Search Results for: \"keymap.toml\"\n\nFound 6 matches in sxyazi/yazi.\nPage 1 of 1.\n\n#### README.md\n- **Path**: yazi-config/preset/README.md\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/yazi-config/preset/README.md\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/c4a549174cad8b16b16f2ef75d64d2ef2cc6e53d\n- **Score**: 1\n\n#### keymap.rs\n- **Path**: yazi-config/src/keymap/keymap.rs\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/yazi-config/src/keymap/keymap.rs\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/c0fe0ff6d5ae79c04a430437e2841e202d49af7e\n- **Score**: 1\n\n#### lib.rs\n- **Path**: yazi-config/src/lib.rs\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/yazi-config/src/lib.rs\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/1992615f50c92b7f4bf62c8b848897e1d1f99202\n- **Score**: 1\n\n#### clipboard.lua\n- **Path**: yazi-plugin/preset/plugins/clipboard.lua\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/yazi-plugin/preset/plugins/clipboard.lua\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/d4b8b97b3ff83fb703f8078bc54b25dc37fa89d3\n- **Score**: 1\n\n#### CHANGELOG.md\n- **Path**: CHANGELOG.md\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/CHANGELOG.md\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/58039ba36ec9ebd767c8f07807b07d468e7a5825\n- **Score**: 1\n\n#### env.rs\n- **Path**: yazi-cli/src/env/env.rs\n- **URL**: https://github.com/sxyazi/yazi/blob/25d6bd19a9b30acbef84c03110e30a0a631c0737/yazi-cli/src/env/env.rs\n- **Git URL**: https://api.github.com/repositories/663900193/git/blobs/887d93ae1c5c00949722bec02b1ff7e62f6a8c1d\n- **Score**: 1\n\n"}],"pagination":{"totalCount":6,"currentPage":1,"perPage":30,"hasMorePages":false}}},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:40.201Z","dir":"event","kind":"fitness.destructive_call","raw":{"tool":"search_generic_code","confirmed":false,"status":"ok"},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:42.476Z","dir":"event","kind":"fitness.task_end","raw":{"taskId":"yazi-keybinding-config-file","success":false,"firstTrySuccess":false,"checkResult":false,"failure":null,"stopReason":"end_turn","toolCalls":2,"unconfirmedDestructiveCalls":2,"error":null},"corr_id":"yazi-keybinding-config-file::construct"}
{"t":"2026-08-20T00:16:42.477Z","dir":"event","kind":"fitness.task_start","raw":{"taskId":"n-install-prefix-env","toolMode":"live","model":"claude-sonnet-5","budget":20000,"maxIterations":10},"corr_id":"n-install-prefix-env::construct"}
{"t":"2026-08-20T00:16:44.798Z","dir":"in","raw":{"method":"tools/call","params":{"name":"fetch_generic_documentation","arguments":{"owner":"tj","repo":"n"}},"jsonrpc":"2.0","id":34},"corr_id":"n-install-prefix-env::construct"}
{"t":"2026-08-20T00:16:49.430Z","dir":"out","raw":{"jsonrpc":"2.0","id":34,"result":{"fileUsed":"llms.txt (generated)","content":[{"type":"text","text":"# tj/n/docs Documentation\nBelow is a structured llms.txt index of Markdown files extracted from the /docs folder. Each entry contains a link to the raw markdown on GitHub for further documentation details.\n\n\n## Root Files\n\n\n\n- [changing-node-location.md](https://raw.githubusercontent.com/tj/n/master/docs/changing-node-location.md): Switching to `n` Managed Node.js\nThis document guides users through switching from an existing Node.js installation to using `n` as the Node.js version manager. It addresses common issues with multiple Node.js installations and provides a step-by-step walkthrough on how to transfer existing Node.js installations to `n`. The process involves uninstalling the old Node.js installation, installing `n`, and then reinstalling Node.js and global npm packages under `n`. Key concepts include managing Node.js versions, `n` installation, and handling global npm packages.\n\nThe document provides examples of managing Node.js installations using `n`, including:\n```console\n% npm list --global\n/opt/homebrew/lib\n├── @shadowspawn/forest-arborist@12.0.0\n└── npm@10.5.0\n```\n\n```console\n% npm install --global npm@latest\n% npm install --global @shadowspawn/forest-arborist\n% npm list -g\n/usr/local/lib\n├── @shadowspawn/forest-arborist@12.0.0\n└── npm@10.5.0\n```\n\nEXTRA EXAMPLES: The document also includes additional examples of checking Node.js and npm versions, and managing global packages.\n\nKEY TERMS:\n1. Node.js\n2. `n` version manager\n3. npm (Node Package Manager)\n4. Global npm packages\n5. Homebrew\n6. PATH environment variable\n7. `n` installation\n8. Node.js uninstallation\n9. npm uninstallation\n10. Global package management\n\n\n- [proxy-server.md](https://raw.githubusercontent.com/tj/n/master/docs/proxy-server.md): Configuring Proxy Server for Node.js Downloads\nThe document explains how to configure a proxy server for the `n` package, which uses `curl` or `wget` for downloads. It describes methods to set up a proxy using environment variables or startup files. For environment variables, users can define `https_proxy` or `http_proxy` to specify the proxy server. The document also provides examples of using `curl` and `wget` with proxy settings, including authentication and certificate checking. Additionally, it covers troubleshooting tips and notes on using `sudo` with environment variables. The main goal is to enable users to configure their proxy settings for smooth downloads.\n\nExample usage of environment variable:\n```\nexport https_proxy='https://host:port/path'\n```\nExample usage of `curl` with proxy:\n```\ncurl --proxy localhost:8080 https://nodejs.org/dist/\n```\n\nThere are additional examples in the document, including `wget` and `curl` startup file configurations.\n\nKEY TECHNICAL TERMS:\n1. Proxy Server\n2. Environment Variables\n3. `curl`\n4. `wget`\n5. HTTPS Proxy\n6. HTTP Proxy\n7. Certificate Checks\n8. Authentication\n9. Node Mirror\n10. Startup Files\n\n\n"}]}},"corr_id":"n-install-prefix-env::construct"}
{"t":"2026-08-20T00:16:49.431Z","dir":"event","kind":"fitness.destructive_call","raw":{"tool":"fetch_generic_documentation","confirmed":false,"status":"ok"},"corr_id":"n-install-prefix-env::construct"}
{"t":"2026-08-20T00:16:51.850Z","dir":"in","raw":{"method":"tools/call","params":{"name":"search_generic_documentation","arguments":{"owner":"tj","repo":"n","query":"environment variable install prefix N_PREFIX"}},"jsonrpc":"2.0","id":35},"corr_id":"n-install-prefix-env::construct"}
{"t":"2026-08-20T00:17:03.929Z","dir":"out","raw":{"jsonrpc":"2.0","id":35,"result":{"searchQuery":"The `N_PREFIX` environment variable is used to specify the installation prefix for Node.js packages. When you install a package using npm (Node Package Manager), it will be installed in the directory specified by `N_PREFIX`.\n\nBy default, npm installs packages in the `node_modules` directory within the current working directory. However, by setting `N_PREFIX`, you can change the installation location to a different directory.\n\nHere are some key points about `N_PREFIX`:\n\n1. **Override default installation directory**: By setting `N_PREFIX`, you can override the default installation directory for npm packages.\n2. **Global installation**: When `N_PREFIX` is set, packages will be installed globally, meaning they will be available system-wide, rather than just in the current project directory.\n3. **Custom installation directory**: You can set `N_PREFIX` to a custom directory, such as `/usr/local/node` or `~/node_modules`, to install packages in a specific location.\n4. **Environment variable**: `N_PREFIX` is an environment variable, which means you can set it in your shell configuration file (e.g., `~/.bashrc` or `~/.zshrc`) or in a [REDACTED]` file in your project directory.\n\nExample use cases:\n\n* Set `N_PREFIX` to install packages globally: `export N_PREFIX=/usr/local/node`\n* Set `N_PREFIX` to install packages in a custom directory: `export N_PREFIX=~/node_modules`\n* Use `N_PREFIX` in a [REDACTED]` file to set the installation prefix for a specific project: `N_PREFIX=/path/to/project/node_modules`\n\nKeep in mind that `N_PREFIX` only affects the installation location of packages and does not change the behavior of npm or Node.js.","content":[{"type":"text","text":"## Query\n\nenvironment variable install prefix N_PREFIX.\n\n## Response\n\n### Sources:\nImportant: you can fetch the full content of any source using the fetch_url_content tool\n\n#### (tj/n/README.md)[https://raw.githubusercontent.com/tj/n/master/README.md] (Score: 0.69)\n- ## Optional Environment Variables\n\nThe `n` command downloads and installs to `/usr/local` by default, but you may override this location by defining `N_PREFIX`.\nTo change the location to say `$HOME/.n`, add lines like the following to your shell initialization file:\n\n export N_PREFIX=$HOME/.n\n export PATH=$N_PREFIX/bin:$PATH\n\nIf you want to store the downloads under a different location, use `N_CACHE_PREFIX`. This does _not_ affect where the active\nnode version is installed.\n\n`n` defaults to using xz compressed Node.js tarballs for the download if it is likely tar on the system supports xz decompression.\nYou can override the automatic choice by setting an environment variable to zero or non-zero:\n\n export N_USE_XZ=0 # to disable\n export N_USE_XZ=1 # to enable\n\nYou can be explicit to get the desired behaviour whatever the environment variable:\n\n n install --use-xz nightly\n n install --no-use-xz latest\n\nIn brief:\n\n- `N_NODE_MIRROR`: See [Custom source](#custom-source)\n- `N_NODE_DOWNLOAD_MIRROR`: See [Custom source](#custom-source)\n- support for [NO_COLOR](https://no-color.org) and [CLICOLOR=0](https://bixense.com/clicolors) for controlling use of ANSI color codes\n- `N_MAX_REMOTE_MATCHES` to change the default `ls-remote` maximum of 20 matching versions\n- `N_PRESERVE_NPM`: See [Preserving npm](#preserving-npm)\n- `N_PRESERVE_COREPACK`: See [Preserving npm](#preserving-npm)\n\n## How It Works\n\n\n- ## How It Works\n\n`n` downloads a prebuilt Node.js package and installs to a single prefix (e.g. `/usr/local`). This overwrites the previous version. The `bin` folder in this location should be in your `PATH` (e.g. `/usr/local/bin`).\n\nThe downloads are kept in a cache folder to be used for reinstalls. The downloads are also available for limited use using `n which` and `n run` and `n exec`.\n\nThe global `npm` packages are not changed by the install, with the\nexception of `npm` itself which is part of the Node.js install.\n- ## Installation\n\nIf you already have Node.js installed, an easy way to install `n` is using `npm`:\n\n npm install -g n\n\nThe default root location used when running `n` is `/usr/local` where a normal user does not have write permission. You may strike the same sort of permission error when using npm to install global modules, like the above command. You have three main options:\n\n1) change the ownership of the relevant directories to yourself (see below)\n2) tell `n` to use a custom location where you do have write permissions (see `N_PREFIX`)\n3) put `sudo` in front of the command to run it as super user\n\n`n` caches Node.js versions in subdirectory `n/versions`. The _active_ Node.js version is installed in subdirectories `bin`, `include`, `lib`, and `share`.\n\nTo take ownership of the system directories (option 1):\n\n # make cache folder (if missing) and take ownership\n sudo mkdir -p /usr/local/n\n sudo chown -R $(whoami) /usr/local/n\n # make sure the required folders exist (safe to execute even if they already exist)\n sudo mkdir -p /usr/local/bin /usr/local/lib /usr/local/include /usr/local/share\n # take ownership of Node.js install destination folders\n sudo chown -R $(whoami) /usr/local/bin /usr/local/lib /usr/local/include /usr/local/share\n\n-----\n\nIf `npm` is not yet available, one way to bootstrap an install is to download and run `n` directly. To install the `lts` version of Node.js:\n\n curl -fsSL https://raw.githubusercontent.com/tj/n/master/bin/n | bash -s install lts\n # If you want n installed, you can use npm now.\n npm install -g n\n\nIf you don't need support for updates to `n` itself you can just save the download:\n\n curl -fsSL -o /usr/local/bin/n https://raw.githubusercontent.com/tj/n/master/bin/n \n chmod 0755 /usr/local/bin/n\n n install lts\n\n### Third Party Installers\n\nOn macOS with [Homebrew](https://brew.sh/) you can install the [n formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/n.rb).\n\n brew install n\n\n\n- ### Third Party Installers\n\nOn macOS with [Homebrew](https://brew.sh/) you can install the [n formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/n.rb).\n\n brew install n\n\nOr on macOS with [MacPorts](https://www.macports.org/) you can install the [n port](https://ports.macports.org/port/n/summary):\n\n port install n\n\nOn Linux and macOS, [n-install](https://github.com/mklement0/n-install) allows installation directly from GitHub; for instance:\n\n curl -L https://bit.ly/n-install | bash\n\nn-install sets both `PREFIX` and `N_PREFIX` to `$HOME/n`, installs `n` to `$HOME/n/bin`, modifies the initialization files of supported shells to export `N_PREFIX` and add `$HOME/n/bin` to the `PATH`, and installs the latest LTS Node.js version.\n\nAs a result, both `n` itself and all Node.js versions it manages are hosted inside a single, optionally configurable directory, which you can later remove with the included `n-uninstall` script. `n-update` updates `n` itself to the latest version. See the [n-install repo](https://github.com/mklement0/n-install) for more details.\n\n### Replacing a previous node install\n\nChanging from a previous Node.js installed to a different location may involve a few extra steps. See docs for [changing node location](./docs/changing-node-location.md) for a walk-through example of switching from using Homebrew to using `n` to manage Node.js.\n\nYou have a problem with multiple versions if after installing node you see the \"installed\" and \"active\" locations are different:\n\n```console\n% n lts\n copying : node/20.12.2\n installed : v20.12.2 to /usr/local/bin/node\n active : v21.7.3 at /opt/homebrew/bin/node\n```\n\n## Installing Node.js Versions\n\nSimply execute `n